Replies: 2 comments
-
Looking at #4767 this is a step toward v1.0 so users should be prepared for an inevitable breaking change. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The latest commit on the 'main' (5afa224) seems to be an intentional breaking change, but I believe many configs are using
ts_configs
(even README): https://github.com/nvim-treesitter/nvim-treesitter#moduleswhich will start to break when merged. I use the latest master/main branch to be adventurous. I was guessing that this might be a part of v1.0.
Is this really a necessary (breaking) change? Can we have this documented clearly at least, or can we have some backward compatibility (e.g., having some deprecation warning when the old module is used)? Neither #4767, the commit message, nor any issue have mentioned such an incompatible change.
I can see that if this was intentional all users have to migrate and catch up the team's decision, but any help or feedback would be appreciated. /cc @clason
Beta Was this translation helpful? Give feedback.
All reactions