The proposed feature seems to be feasible. I would suggest creating a pull
request and discussing it with the plugin maintainer.
For testing, I was thinking of making some html files with and without the
> strings to find, and seeing if the summary contains the right errors ...
> does that
I propose to add an option to scan-build to ignore problem reports
containing certain strings (user-specified list of strings to ignore) in
certain parts of the problem report.
Rationale and explanation:
We use clang-scanbuild to find problems in our codebase. But it finds
problems related
