{{ message }}
Repository navigation
.htmlhintrc silently ignored if not valid JSON #662
Description
If the .htmlhintrc is not valid JSON, the linter silently ignores it and uses a default config.
For example, I had made the mistake of keeping a trailing comma:
{
"attr-lowercase": false,
}
The default config has "attr-lowerclase": true and I received a lot of unwanted errors. It took me a while to figure out that the malformatted JSON was the culprit.
It would be helpful if the linter at least displayed a warning log message upon execution if it cannot parse the config file.
Activity
[-].htmlhintrc silently ignored if not valid JSON[/-][+]`.htmlhintrc` silently ignored if not valid JSON[/+]marwinburesch commentedon Jul 20, 2021
I agree, for example the docs use single quotes in the examples, but it is only valid with double quotes
stale commentedon Sep 19, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
feat: display warning log message when it can not parse config
feat: display warning log message when it can not parse config
feat: display warning log message when it can not parse config
feat: display warning log message when it can not parse config
feat: display warning log message when it can not parse config
feat(cli): display warning log message when it can not parse config
feat(cli): display warning log message when it can not parse config (#…