I suggest implementing a command that resolves the linter configuration for a given path and prints it to the console in JSON / YAML format. For example:
aglint --print-config path/to/file.txt
or
aglint --print-config path/to/folder
or for the actual folder:
aglint --print-config .
This can be a useful tool for various debugging purposes.
Optionally, we can also list the chain of configuration files from which the configuration was compiled by merging.
scripthunter7
commented
1 year ago
I suggest implementing a command that resolves the linter configuration for a given path and prints it to the console in JSON / YAML format. For example:
or
or for the actual folder:
This can be a useful tool for various debugging purposes.
Optionally, we can also list the chain of configuration files from which the configuration was compiled by merging.