fix: ensure syntax blocks for ebnf are marked as such #16837
Merged
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.
I see that this was done in the past in
https://github.com/lampepfl/dotty/pull/14958/files, but then reverted in
#14958. Like many commits, there
really isn't an explanation of the revert, but from reading between the
lines I assume the
;
was the actual issue, not the syntaxhighlighting. As it was pointed out, syntax.js doesn't actually support
ebnf
. They do say they supportbnf
, but that didn't really work when Iwas testing. Either way, this pr makes sure that we do mark the
snippets as
ebnf
. The reason for this isn't necessarily so that weget syntax highlighting for these, but so that syntax.js doesn't infer
the wrong type of syntax and provide odd highlighting like we currently
have. This also helps to ensure screen readers know what type of
codeblock this is.
fixes #14697