Merged
Conversation
- If a grammar has a base language, it should always be resolved - Fix `getLanguage()`: `language` can already be a resolved grammar if it is taken from `this.languages` Remove extra line
DmitrySharabin
force-pushed
the
language-class
branch
from
faa3319 to
7ee67f8
Compare
LeaVerou
approved these changes
May 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
getLanguage():languagecan already be a resolved grammar if it is taken fromthis.languagesWith the change, code blocks in HTML, CSS, and JS can be highlighted correctly without needing to specify the base languages (
clikeandxml):Without the change, we need to explicitly specify them: