It is sometimes be necessary to include a non-inclusive term, for instance, because an external library uses it as a parameter name, or because it is in the name of a branch in another repo that I do not control the name of.
I would like to be able to flag such lines with an indication for blocklint that I know about them and don't want to be warned.
This is particularly relevent when using blocklint as part of a CI/CD pipeline where output from blocklint is treated as an error.
This PR adds a directive: "blocklint: pragma", that instructs blocklint to ignore any lint on a line containing that suffix.
Included are tests demonstrating how this can be used.
troycomi
commented
3 years ago
It is sometimes be necessary to include a non-inclusive term, for instance, because an external library uses it as a parameter name, or because it is in the name of a branch in another repo that I do not control the name of.
I would like to be able to flag such lines with an indication for blocklint that I know about them and don't want to be warned. This is particularly relevent when using blocklint as part of a CI/CD pipeline where output from blocklint is treated as an error.
This PR adds a directive: "blocklint: pragma", that instructs blocklint to ignore any lint on a line containing that suffix. Included are tests demonstrating how this can be used.