Can arguments of a message contain hyperlink markup? #639
Replies: 2 comments
-
A bit related to #597. |
Beta Was this translation helpful? Give feedback.
-
A If SARIF consumers first replace parameter placeholders with argument values and then parse the resulting string, the SARIF producer may have to duplicate the argument values in order to encode them for each format: {
"text": "The {0} tag is obsolete.",
"markdown": "The **{1}** tag is obsolete.",
"arguments": [ "<ISINDEX>", "\\<ISINDEX\\>" ]
} If SARIF consumers first parse the template and then replace parameter placeholders with argument values, the SARIF producer can instead share the same argument values for all formats: {
"text": "The {0} tag is obsolete.",
"markdown": "The **{0}** tag is obsolete.",
"arguments": [ "<ISINDEX>" ]
} Because of this, I'm inclined to believe that the latter interpretation is intended. |
Beta Was this translation helpful? Give feedback.
-
When a message in a result contains placeholders (SARIF-2.1.0 §3.11.5), must the SARIF consumer first replace the placeholders with argument values and then parse the result for embedded links (SARIF-2.1.0 §3.11.6)? If so, this would allow the SARIF producer to emit links within the argument values themselves, but might also require the SARIF producer to backslash-escape some characters in the argument values in order to prevent the consumer from misparsing them as links.
Hypothetical example:
Beta Was this translation helpful? Give feedback.
All reactions