forked from windwp/nvim-ts-autotag
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve how setup is handled #5
Comments
PriceHiller
added a commit
that referenced
this issue
May 15, 2024
This deprecates the old setup layout Closes #5
PriceHiller
added a commit
that referenced
this issue
May 15, 2024
This deprecates the old setup layout Closes #5
PriceHiller
added a commit
that referenced
this issue
May 15, 2024
This deprecates the old setup layout Closes #5
PriceHiller
added a commit
that referenced
this issue
May 15, 2024
This deprecates the old setup layout Closes #5
PriceHiller
added a commit
that referenced
this issue
May 15, 2024
This deprecates the old setup layout Closes #5
PriceHiller
added a commit
that referenced
this issue
May 19, 2024
This deprecates the old setup layout Closes #5
windwp
pushed a commit
to windwp/nvim-ts-autotag
that referenced
this issue
May 20, 2024
This deprecates the old setup layout Closes PriceHiller#5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently setting up the plugin is a right pain with little extensibility.
For instance, if a TS parser upstream changes all downstream users of this plugin are entirely dependent on us to update our search patterns. A lot of issues prior to this fork stemmed from the lack of exensibility.
Thus, we should enhance the config and make it easier to update and extend from a user's perspective.
The text was updated successfully, but these errors were encountered: