chore!: remove internal filetype to parser name aliases #327
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
This was referenced Apr 11, 2023
Owner
Author
|
cc @jmbuhr (as this PR essentially reverts your changes) |
Contributor
|
Perfect, thanks for the update. This means my changes are no longer necessary as the mapping also lives in nvim-treesitter now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes the workaround needed for converting filetype to parser name. Neovim now provides proper API to deal with this ambiguity, which is also respected by nvim-treesitter and for most cases this conversion is automatic.
This was introduced in
Supersedes #326
Fixes #325