Skip to content

fix(lib): use find_syntax_by_token for language matching #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

arHSM
Copy link

@arHSM arHSM commented May 29, 2025

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

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant