Orion has powerful linting tools that detect potential programming problems as you type. Â Our tooling provides a huge list of rules, everything from basic syntax mistakes like missing semicolons to multi-file function reference checking. Â Try out the latest at orionhub.org.
The linting tools are based on ESLint, but we have our own set of rule implementations. Â These rules are used to test the code in your editor as you type. Â Discovered issues are marked with annotations, squiggly yellow or red underlines reminiscent of Eclipse.
Hovering over the annotation will give you a tooltip hover with a description of the problem. Â In addition the hover may show buttons representing quick fixes. Â Quick fixes modify your code to fix the linting problem. Â While no quick fix should ever break your code, you can always undo the effects (Ctrl+Z). Â Most fixes will automatically fix the code, adding or removing content, but a few will start a rename operation requiring you to type a new name.
Some quick fixes also have a ‘Fix All’ option which will fix all instances of that problem in your file.
Our rule list continues to expand. Â We have incorporated rule implementations from ESLint, added rules specific to our translations support, and now we are working at writing rules that use our type inference engine to detect reference problems between scripts.
If a rule goes against the programming practices your dev team follows, you can change which rules run on the JavaScript Validation settings page.
If you want to run a linting pass on multiple files you can use the Show Problems command. Â Select a file or folder in the file navigator, right click and press Show Problems… (Ctrl+Alt+P). Â This will run the linter on all of the files and display them in a table. Â You can click on any problem to navigate to it.
