Feature description
A separate command beside check and fix, maybe named status or info, to get information about the usage in the targets. This should include for how many files there is at least one EditorConfig property set and how many files have a specific EditorConfig property set (including amount per property value). Beside the total amount percentages would be also of interested. Some options for the command could be to give a specific property or request detailed results for all of them. A very verbose option to list all respective files (with a specific property set or even property value) would be also nice.
Benefits
This would allow verifying if all files (or all relevant files) of a project are covered with the (relevant) EditorConfig properties or not. Furthermore, one could check the respective list of files, if some files should not have an EditorConfig (e.g., binary files).
Resources
No response
### Feature description
A separate command beside `check` and `fix`, maybe named `status` or `info`, to get information about the usage in the targets. This should include for how many files there is at least one EditorConfig property set and how many files have a specific EditorConfig property set (including amount per property value). Beside the total amount percentages would be also of interested. Some options for the command could be to give a specific property or request detailed results for all of them. A very verbose option to list all respective files (with a specific property set or even property value) would be also nice.
### Benefits
This would allow verifying if all files (or all relevant files) of a project are covered with the (relevant) EditorConfig properties or not. Furthermore, one could check the respective list of files, if some files should not have an EditorConfig (e.g., binary files).
### Resources
_No response_