I think it would be very useful to provide each issue fingerprint within its description in the linter report.
There are some rules that you don't want to disable and it's impossible to fix by any means.
For example, I'm customizing the behavior of the markdownlint engine for one of my projects. I have disabled the rule no-inline-html, but I want to keep the rule that checks the line length. I have some URLs in my markdown that are longer than the default threshold of 80 chars. I could increase it by modifying with .mdlrc (for enabling/disabling rules) and .mdlrc.rb (for customizing rules; for example, the default maximum line length).
But then the new length would apply to all lines in each markdown file. I would like to exclude those exceptions by manually providing its issue fingerprints inside the project's .codeclimate.yml, but right now I can only do that after I get the web report or manually run the CodeClimate cli on the command line.
I think it would be very useful to provide each issue fingerprint within its description in the linter report.
There are some rules that you don't want to disable and it's impossible to fix by any means.
For example, I'm customizing the behavior of the
markdownlintengine for one of my projects. I have disabled the ruleno-inline-html, but I want to keep the rule that checks the line length. I have some URLs in my markdown that are longer than the default threshold of 80 chars. I could increase it by modifying with.mdlrc(for enabling/disabling rules) and.mdlrc.rb(for customizing rules; for example, the default maximum line length).But then the new length would apply to all lines in each markdown file. I would like to exclude those exceptions by manually providing its issue fingerprints inside the project's
.codeclimate.yml, but right now I can only do that after I get the web report or manually run the CodeClimate cli on the command line.