Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Orion/Plan/Language Tools
Contents
Orion 13.0 (Oct 2016)
This is a high level roadmap for Language Tools in the Orion editor. Items here are not guaranteed to be found in any release.
For more details on what is being worked on, have a look at the current bugs tagged for 13.0
Provide a full featured tooling plugin for Brackets
Support ES7/ES2016 (496859)
Make it easier to update 3rd party library (specifically Tern)
ES6-ify Orion {{PlanItem|Mark guessed proposals||}
Use HTMLLint (476910)
Orion 12.0 (June 2016)
Support .eslintrc files (461228)
Investigate making the entire JS bundle a worker (484136)
Investigate making the JavaScript tools consumable outside of Orion (486482)
Support cross file linting (486577)
Improve logical file lookup performance (457872)
Orion 11.0 (Feb 2016)
Search for references and declarations (471947)
Tern Plugin for JSDoc (468188)
Fully support .tern-project files (476062)
Update to Tern 0.16.0 (482509)
Update to Acorn 2.6.4 (482512)
Update to ESLint 1.9.0 (482505)
Update to Doctrine 0.7.1 (482526)
Update to Estraverse 4.1.1 (482529)
Update to EScope 3.2.0 (482612)
Allow quick fixes to apply to all problems in file (475852)
Orion 10.0 (Nov 2015)
Support RequireJS as a target development environment
Support Node Modules as a target development environment
Support Plain HTML as a JavaScript target development environment (465816)
Search for references and declarations (471947)
Improve HTML content assist (471446)
Improve CSS content assist (458306)
Make content assist discoverable (472071)
Display parameters when auto completing functions
Investigate incremental parsing (460256)
Make comment keybindings work for CSS/HTML (469939)
Support ES6 constructs (460728)
Update to latest Esprima parser (473765)
Update to Tern 0.10.0 (465034)
Update to Tern 0.12.0 (473111)
Update to Acorn 2.0.4 (472303)
Update to latest ESLint 0.15.1
Other ideas
Make tooltips part of the customizable theme
Replace quickfix commands with a service API
Use pages or type filtering to reduce size of content assist proposal list
Style individual proposals (show deprecated functions) (473204)
Rich visuals in tooltips and content assist (guides/tools/wizards)
Hyperlinks in editor text for navigation
Better workflow for changing settings
Allow sub categories in settings