Skip to content
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

fix(treesitter): enforce lowercase language names #28546

Merged
merged 2 commits into from
Apr 28, 2024

Conversation

clason
Copy link
Member

@clason clason commented Apr 28, 2024

Problem: On case-insensitive file systems (e.g., macOS), has_parser
will return true for uppercase aliases, which will then try to inject
the uppercase language unsuccessfully.

Solution: Enforce and assume parser names to be lowercase when
resolving language names.

Problem: On case-insensitive file systems (e.g., macOS), `has_parser`
will return `true` for uppercase aliases, which will then try to inject
the uppercase language unsuccessfully.

Solution: Enforce and assume parser names to be lowercase when
resolving language names.
Problem: On case-insensitive file systems (e.g., macOS), `has_parser`
will return `true` for uppercase aliases, which will then try to inject
the uppercase language unsuccessfully.

Solution: Enforce and assume parser names to be lowercase when
resolving language names.
@clason clason merged commit 26b5405 into neovim:master Apr 28, 2024
29 checks passed
@clason clason deleted the fix/ts-lowercase branch April 28, 2024 14:27
@github-actions github-actions bot removed the request for review from bfredl April 28, 2024 14:28
huangyingw pushed a commit to huangyingw/neovim that referenced this pull request May 31, 2024
* fix(treesitter): enforce lowercase language names

Problem: On case-insensitive file systems (e.g., macOS), `has_parser`
will return `true` for uppercase aliases, which will then try to inject
the uppercase language unsuccessfully.

Solution: Enforce and assume parser names to be lowercase when
resolving language names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants