What is new and awesome in Orion 11.0

With Orion 11.0 officially released, it is time again to share with you the new & noteworthy items developed during this release.  Unlike previous announcements we will be posting more in-depth articles about the new functionality and how to use it.


Where is this function used?  Where is it declared?  What if I need to change its signature? Global search is not the only tool for answering these questions if you use Orion 11.0.  Find All References can search through your project or workspace find potential matches and then figure out which ones are actually referencing the function (or variable) you are interested in.  Orion will sort all the matches into reference types and then provide a green check if we are sure this is a matching reference, a question mark if it is a possible reference, or a red X if it is not a reference (but matches the search text).  You can take it a step further and refactor the contents of multiple files at once.  There is a full write-up on Planet Orion with the details.


Documentation of your APIs not only is good practice, it makes the existing language tools work better.  When your JSDoc (add it to any function using Alt+Shift+J) specifies the type of a function’s arguments and returns, the tooling can offer more accurate content assist and hovers.  To help you fill in these types we now offer content assist inside JSDoc.


Our JavaScript linting (based on the ESLint validator) continues to expand with new rules, new quick fixes and more.  Remember that all of the rules can have their severity configured on the JavaScript Validation settings page.  The excited new feature for 11.0 is ‘fix all’, applying quick fixes to the entire file.  Open up a file with warnings throughout and quickly apply safe fixes to clean up the whole file.  There is a lot happening in our validation support during this release and the next, so we will have a more in-depth look at the features in an upcoming article.



Many of the JavaScript tools work closely with our type inferencing engine, Tern.  To get the most accurate content assist, correct navigation and detailed hovers it is best to have your project set up in a way Tern can easily analyze your code.  The best way to provide our tooling and Tern with this information is through creation of a .tern-project file.  In the coming weeks we will give a full write-up on how to do this and exactly how it will benefit your project.


Our tooling for HTML has seen impressive improvements during this release.  The parser we use was entirely replaced with HTMLParser2 providing us with much more accurate ranges and more recovery options for incomplete HTML.  Content assist has expanded to support accessibility attributes, specifically ARIA roles.  We also provide assist for many attribute values, not just the elements and attributes.  See the full write up here.


We also highlight the selected tag and its matching tag close.  Have Show Occurrences option turned on in the Editor Settings to see it.

The Orion client continues to improve each release.  There were more than 150 bugs fixed during 11.0.  We have updated the libraries that we depend on to pick up their hard work:   Acorn 2.6.4 Doctrine 0.7.1 Estraverse 4.1.1 ESLint 1.9.0.  Our test suites continue to expand, the shining example being JavaScript tools which has 2232 tests and growing.

Try it right now at orionhub.org!


This entry was posted in New & Noteworthy. Bookmark the permalink.