Command to validation all properties in .editorconfig files #44

BaumiCoder commented 2026年05月31日 10:59:50 +02:00

Feature description

A separate command for ecformat, maybe called validate, that only checks that the values of the properties in all .editorconfig files are correct. For example that indent_style is tab or space not something else. Maybe the handling of spelling_language from #8 could also move to this command. The command line switches could be identically or at least similar to check and fix. However, one edge for the targets could be worth to consider differently. If a .editorconfig file is directly one of the target, should it be only validated directly or also all other .editorconfig files that may apply to it?

Benefits

This would allow also check (separately) that .editorconfig files themselves contains no error. This would for example enable to use ecformat for a respective separate pre-commit hook for changes to these files.

Resources

• specification of all properties

### Feature description A separate command for ecformat, maybe called `validate`, that only checks that the values of the properties in all `.editorconfig` files are correct. For example that `indent_style` is `tab` or `space` not something else. Maybe the handling of `spelling_language` from #8 could also move to this command. The command line switches could be identically or at least similar to `check` and `fix`. However, one edge for the targets could be worth to consider differently. If a `.editorconfig` file is directly one of the target, should it be only validated directly or also all other `.editorconfig` files that may apply to it? ### Benefits This would allow also check (separately) that `.editorconfig` files themselves contains no error. This would for example enable to use ecformat for a respective separate pre-commit hook for changes to these files. ### Resources - [specification of all properties](https://spec.editorconfig.org/#supported-pairs)

BaumiCoder commented 2026年06月03日 17:14:36 +02:00

Another validation could be that no .editorconfig file or even no section inside one is unused. This means that it applies to no file. That could be an optional part of the command or a warning from it. Such situations can be also indented, such as for files which are not committed to the git repository.

Another validation could be that no `.editorconfig` file or even no section inside one is unused. This means that it applies to no file. That could be an optional part of the command or a warning from it. Such situations can be also indented, such as for files which are not committed to the git repository.