![]() ![]() If the necessary severity is not on the list, click Edit Severities to create a new one.įrom the Highlighting in editor list, select the style that you want to use to highlight code fragments in the editor. You can also right-click the inspection and select the severity level from the context menu. Make sure that it is enabled.įrom the Severity list, select a new severity level. Select the profile that you want to modify and then choose an inspection from the list. Press Ctrl+Alt+S to open the IDE settings and select Editor | Inspections. ![]() Severity levels are designed to indicate problems, they don't have any impact on the code execution: if you change the severity for spelling mistakes from Typo to Error, this won't affect the execution of your application. No highlighting, only fix: provides no code highlighting the list of available fixes is invoked by pressing Alt+Enter.įor every severity, you can configure its own highlighting style in the editor. This severity is not marked on the error stripe and does not have a default highlighting style, but you can choose one from the list of existing styles or configure your own. This severity comes from the bundled Grazie plugin.Ĭonsideration: code fragments that can be improved. Server Problem : problems that come from an external build server, for example, from TeamCity. ![]() Weak Warning : code fragments that can be improved or optimized (redundant code, duplicated code fragments, and so on). Warning : code fragments that might produce bugs or require enhancement. In PhpStorm, there is a set of predefined severity levels: Inspection severity levels indicate how seriously the detected code problems affect your project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |