Skip to content

Encourage escaping of square brackets and backslashes in text messages#768

Open
adityasharad wants to merge 1 commit intoeditor-revision-2026-03-05from
adityasharad/text-messages-bracket-escaping-guidelines
Open

Encourage escaping of square brackets and backslashes in text messages#768
adityasharad wants to merge 1 commit intoeditor-revision-2026-03-05from
adityasharad/text-messages-bracket-escaping-guidelines

Conversation

@adityasharad
Copy link
Copy Markdown
Contributor

@adityasharad adityasharad commented Mar 5, 2026

Closes #658.
Closes #597.

These characters may be backslash-escaped, even outside link text.
They should be backslash-escaped if there is ambiguity about whether the text section is an embedded link.
This provides a way to disambiguate, without making any existing SARIF invalid.

For discussion:

  • Should we be stricter and require escaping of these characters always? I chose not to since that would make some existing SARIF invalid.

These characters may be backslash-escaped, even outside link text.
They should be backslash-escaped if there is ambiguity about whether the text section is an embedded link.
Update examples.
This provides a way to disambiguate, without making any existing SARIF invalid.

Addresses #658.
@sthagen
Copy link
Copy Markdown
Contributor

sthagen commented Mar 5, 2026

@Torc-Charles-Wilson please kindly review.

@sthagen sthagen mentioned this pull request Mar 7, 2026
8 tasks
@sthagen sthagen changed the base branch from main to editor-revision-2026-03-05 March 7, 2026 14:20
@sthagen
Copy link
Copy Markdown
Contributor

sthagen commented Mar 7, 2026

Changed target to branch oasis-tcs/sarif-spec/editor-revision-2026-03-05 as usual and discussed during the TC meeting 2026-03-05.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants