Code Inspections in EditorConfig

Reports EditorConfig properties that are no longer supported.

Reports wildcard patterns in the EditorConfig section that contain a duplicate character in the character class, for example [aa].

Reports file patterns that are redundant as there already are other patterns that define the same scope of files or even a broader one. For example, in [{*.java,*}] the first *.java pattern defines a narrower scope compared to *. That is why it is redundant and can be removed.

Reports sections that define the same file pattern as other sections.

Reports sections with an empty header. Section header must contain file path globs in the format similar to one supported by gitignore.

Reports sections that do not contain any EditorConfig properties.

Reports multiple top-level declarations. There can be only one optional “root=true” top-level declaration in the EditorConfig file. Using multiple top-level declarations is not allowed.

Reports property values that do not meet value restrictions. For example, some properties may be only “true” or “false”, others contain only integer numbers etc. If a value has a limited set of variants, use code completion to see all of them.

Reports identifiers that are either unknown or have a wrong type.

Reports sections with wildcard patterns that do not match any files under the directory in which the .editorconfig file is located.

Reports duplicates in lists of values.

Reports subsets of files specified in the current section that overlap with other subsets in other sections. For example: [{foo,bar}] and [{foo,bas}] both contain “foo”.

Reports properties that are already defined in other sections.

For example:

Reports properties that override the same properties defined earlier in the file.

For example:

Reports properties that are redundant when another applicable section already contains the same property and value.

For example:

Reports wildcards that become redundant when the “**” wildcard is used in the same section.

The “**” wildcard defines a broader set of files than any other wildcard. That is why, any other wildcard used in the same section has no affect and can be removed.

Reports properties that miss the required declarations. Refer to the documentation for more information.

Reports space characters in wildcard patterns that affect pattern matching. If these characters are not intentional, they should be removed.

Reports sections that contain too many wildcards. Using a lot of wildcards may lead to performance issues.

Reports commas that cannot be used in the current context. Commas are allowed only as separators for values in lists.

Reports key-value pairs that are not allowed in the current context.

Reports unexpected top-level declarations. Top-level declarations other than “root=true” are not allowed in the EditorConfig file.

Reports lists of values that are used in properties in which lists are not supported. In this case, only a single value can be specified.

Reports properties that are not supported by the IDE. Note: some “ij” domain properties may require specific language plugins.

Reports pattern lists that are either empty {} or contain just one pattern, for example {foo}. The braces are needed only if there are two and more, for example: {foo,bar}

Reports character classes that consist of a single character. Such classes can be simplified to a character, for example [a] → a.

Reports unused declarations. Such declarations can be removed.