fix(lib): use find_syntax_by_token for language matching
#2
Conversation
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
currently `find_syntax_by_extension` is used followed by `find_syntax_by_name`, this means you have to either pass the exact extension or the "pretty"/"formatted" name, i.e, "Javascript" instead of "javascript", however `find_syntax_by_token` handles this for you by doing a case insensitive equality check with the name, and of course it also tries to match the extension first
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
currently
find_syntax_by_extensionis used followed byfind_syntax_by_name, this means you have to either pass the exact extension or the "pretty"/"formatted" name, i.e, "Javascript" instead of "javascript", howeverfind_syntax_by_tokenhandles this for you by doing a case insensitive equality check with the name, and of course it also tries to match the extension first