| Summary: | [outline] Provide an AST view (outline?) | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | JS Tools | Assignee: | Curtis Windatt <curtis.windatt.public> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | curtis.windatt.public |
| Version: | 13.0 | ||
| Target Milestone: | 13.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Rennie
I've run into this problem before as well. I have a working example of doing this with a second outliner. Just need to update the test suite. http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=b4c40611ae84c4fa7297d0a54cd7682410e9b87c Fixed in master I only added one regression test just to ensure it is working. The content matches the AST exactly (node type and range). If we add more content to the outline we will add more tests. I pushed a small update that shows all spec'd properties of the nodes and arranges them in their correct ECMA-named locations. I also added a separate test suite for the outliner that tests the results of the outline for good and broken ASTs. I pushed one further update to filter out redundant information that makes searching for certain syntax painful. |