Or, use the Ctrl-` shortcut and select Look and Feel – High Contrast. You can enable the new theme in the IDE Preferences | Appearance and Behavior | Appearance. It is part of our long-term effort to make the IDE more accessible to everyone and we plan to continue working in this direction.
The big feature from IntelliJ Platform that has landed in this update is the new high-contrast theme. High-contrast theme and accessibility improvements Then select the severity level you want to use instead in the drop-down above the checkbox. To use this, go to Preferences | Editor | Inspections – TSLint or ESLint and clear the checkbox “Use rule severity from the configuration file”. Based on your requests, we have made it possible to ignore the severities in the config file and show everything reported by the linter as errors, warnings, or in custom color. Override severity from ESLint or TSLint configīy default, WebStorm uses the severity levels from the ESLint or TSLint configuration files when highlighting errors and warnings from these linters in the editor. You can disable this behavior in Preferences | Languages and Frameworks | JavaScript – Expand method bodies in completion for overrides. Here’s an example of the generated method: Now, when you want to override a method from the parent class or interface and select it from the completion suggestions, WebStorm will automatically add parameters, super() call and, if possible, the type info. This new option provides suggestions for variable names based on the names of classes, types, and interfaces defined in the project, and the libraries you use and those found in standard APIs.Ĭompletion for overrides adds method body This feature comes from IntelliJ IDEA’s support for Kotlin, where it first appeared and is on by default. With the new Extract ruleset intention, you can move selected properties to a new block and then modify its selector.Īmong the IDE JavaScript preferences, you can find a new option called Suggest variable names. The new intention Replace var() with its fallback value allows you to quickly remove CSS custom properties/variables from the code:
In the advanced formatting dialog ( Shift-Alt-Cmd-L), you can enable running Rearrange code every time you reformat the code.Įxtract ruleset and replace var() with its fallback value Once enabled, you can use the Rearrange code action to sort the properties. Use it to enable and configure sorting for the properties inside rulesets. In addition, CSS code style configurations now have the new Arrangement tab. Minimum Blank Lines Around Top-level Block and Around Nested Selector will, on the contrary, add empty lines. Note that this option doesn’t add any lines but only removes extra (the resulting code is on the right): In this example, with the option set to 2, WebStorm will remove one extra empty line. Keep Maximum Blank Lines in Code will remove extra empty lines when you reformat the code (Alt-Cmd-L / ). There are 3 new options located on the Blank lines tab for each language under Preferences | Editor | Code Style | Style Sheets. Second, we’ve made the use of blank lines in the files more configurable. Before, most of the options were inherited from the CSS code style and only indents could be configured for each language.
First, each language now has its own configuration with a full set of options. We have updated the code style options for style sheet languages. When debugging workers in WebStorm, you will see in what thread the breakpoint was hit and you will be able to switch between threads to see the call stack and variables. You also need to pass the –experimental-worker flag to the node. Debugging workers is available in Node.js 10.12 that was released today. WebStorm now provides code completion for the worker threads API and allows you to debug workers. Node.js 10.5 introduced a new experimental feature – worker threads, which can be used for CPU-intensive tasks (check out this blog post for a great overview of the feature). For the full list of issues fixed in this update, see the Release Notes. Here are some of the highlights of WebStorm 2018.3 EAP #6 (build 183.3647.15). Important! WebStorm EAP builds are not fully tested and might be unstable. You can also get notified right from the IDE when a new EAP build is available: go to Preferences | Appearance & Behavior | System Settings | Updates and select “Automatically check updates for Early Access Program”. Toolbox App is the easiest way to get EAP builds. If you’re unfamiliar with our Early Access Program or if you want to catch up on all the new features, check out the previous EAP blog posts. WebStorm 2018.3 Early Preview build #6 is now available!