I've been trying to use WebStorm / PHPStorm but just can't get past the crazy complicated settings screens and cluttered UI. I gave up when trying to convince WebStorm that ES6 needs no semicolons after a line of code. After changing this setting in more than 6 different settings screens, it still wasn't allowed.
Is a matter of getting used to it for sure. I've been using PHPStorm for so long that almost everything comes to me naturally. What you are describing is the code inspection highlights which you have full control of.
You can edit any inspection warning/error directly from the editor without even having to go the setting page:
Place your cursor over the highlighted symbol
Press Alt + Enter to open the intention options or context menu.
Highlight one of the intentions with the arrow keys(↑/↓), an intention usually has an orange light bulb next to it, then press the → key to see additional options.
In the additional options dropdown you will have multiple options which includes disabling the inspection rule altogether and an action that takes you directly to the configuration section to edit the specific inspection rule among other actions.
Thanks for the hint! Of course it's always a matter of getting used to software. PHPstorm certainly has gazillions of options. I just find VS Code more intuitive, with less menus buried deep within other menus.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've been trying to use WebStorm / PHPStorm but just can't get past the crazy complicated settings screens and cluttered UI. I gave up when trying to convince WebStorm that ES6 needs no semicolons after a line of code. After changing this setting in more than 6 different settings screens, it still wasn't allowed.
Just add a Prettier config to your package.json and it will ask and apply code formatting based on those settings to your whole project...
Is a matter of getting used to it for sure. I've been using PHPStorm for so long that almost everything comes to me naturally. What you are describing is the code inspection highlights which you have full control of.
You can edit any inspection warning/error directly from the editor without even having to go the setting page:
Thanks for the hint! Of course it's always a matter of getting used to software. PHPstorm certainly has gazillions of options. I just find VS Code more intuitive, with less menus buried deep within other menus.