New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SARIF 2.1.0 message string lookup #157
Comments
This will require the reportingDescriptor lookup mentioned in #154 (comment). There might be many reportingDescriptor objects with the same reportingDescriptor.id, and the SARIF consumer needs to use result.ruleIndex or reportingDescriptorReference.index to choose the correct reportingDescriptor object, so that it can locate the multiFormatMessageString object in the reportingDescriptor.messageStrings property. The identifiers of messages are not necessarily unique across reportingDescriptor objects; the validator in https://github.com/microsoft/sarif-sdk/ uses "Note_Default" for many different messages. |
I implemented this now. Not really sure how to handle the references within the |
Those should just be displayed as text. If the SARIF producer wants them to be displayed as hyperlinks, it needs to use Markdown link syntax and a separate object to refer to the link target. |
For hyperlinks to the analyzed files, the SARIF producer can use location objects as described in SARIF-v2.1.0 section 3.11.6. Syntax like For hyperlinks to objects in the SARIF log that contains the hyperlinks, the SARIF producer can use the |
I think this is fixed. |
SarifParser does not yet support
message
objects that lack thetext
andmarkdown
properties and instead have anid
property. It would have to locate the message string that corresponds to theid
, as specified in [SARIF-v2.1.0] §3.11.7 Message string lookup.Sample SARIF log that requires message string lookup
(This log was generated by running the https://github.com/microsoft/sarif-sdk/ validator on the SARIF log in #155 (comment). The
SARIF2002
notes recommend formatting SARIF logs in such a way that they require message string lookup.)The text was updated successfully, but these errors were encountered: