GitLab Code Quality reports may omit the "type": "issue" field. The current implementation appears to require this property and therefore fails to detect issues in reports generated by some GitLab Code Quality tools.
Since "issue" is effectively the only valid value for the type field in this context, the property is redundant. The parser could treat a missing type field as "issue" by default, improving compatibility with GitLab-generated reports and third-party report generators.
Was wondering if you are open to that change, or if you accept PRs?
GitLab Code Quality reports may omit the
"type": "issue"field. The current implementation appears to require this property and therefore fails to detect issues in reports generated by some GitLab Code Quality tools.Since "issue" is effectively the only valid value for the type field in this context, the property is redundant. The parser could treat a missing type field as "issue" by default, improving compatibility with GitLab-generated reports and third-party report generators.
Was wondering if you are open to that change, or if you accept PRs?