fix(neovim): fix 0.12 deprecation warning#31
Conversation
`vim.lsp.semantic_tokens.start` is marked as deprecated in Neovim 0.12 and replaced by `vim.lsp.semantic_tokens.enable(true)`. The semantic token highlighting engine is started automatically when a client is attached to the buffer which makes the call to this function unnecessary, and therefore the entire on_attach wrapper can be removed.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughRemoved wrapper logic from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #31 +/- ##
=======================================
Coverage 92.43% 92.43%
=======================================
Files 17 17
Lines 5529 5529
=======================================
Hits 5111 5111
Misses 418 418 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Tested, and seems to indeed be redunant, also on 0.11 Thanks for the contribution <3 |
The LSP plugin for Neovim currently causes a deprecation warning in Neovim >= 0.12:
vim.lsp.semantic_tokens.startis marked as deprecated in Neovim 0.12 and replaced byvim.lsp.semantic_tokens.enable(true).The semantic token highlighting engine is started automatically when a client is attached to the buffer which makes the call to this function unnecessary, and therefore the entire on_attach wrapper can be removed.
Summary by CodeRabbit