Use CWE in findings list report instead of problem type mapping #87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Xanitizer 4.1 we renamed and split up some problem types so that the parser for Xanitizer's XML findings list report format can not map the new problem types to the corresponding CWE number. To reduce necessary changes/commits in case of renamed or new problem types, the parser reads the CWE number directly from the detected finding output in the XML report instead of using an internal problem type <-> CWE number mapping.