Text document version is implemented incorrectly
See original GitHub issueI am using neovim as the client. Whenever I apply a code action, neovim shows a warning saying “Buffer X newer than edits”.
Searching through the Internet points me to this issue on neovim: https://github.com/neovim/neovim/issues/12970.
A quick hack on neovim code shows that in my case, volar is reporting text_document.version
as 5 while neovim is having 14
.
Volar is at version 0.38.1
.
Issue Analytics
- State:
- Created a year ago
- Reactions:6
- Comments:5
Top Results From Across the Web
Problem with versioning of a shared document
my understanding is that you configured versioning settings via library settings > versioning settings > require check out > yes, also you have ......
Read more >What is the best way to version control a text document? - Quora
You can analyse the changes you have made and identify where new bugs have been introduced. By implementing a good quality version control...
Read more >Version control concepts and best practices
This document is a brief introduction to version control. ... Each commit should have a single purpose and should completely implement that purpose....
Read more >Don't let version confusion destroy your writing process
In order to track down what has happened, you'll need to resort to version comparison tools and untangle the history of the edits....
Read more >Version control: Effective use, issues and thoughts, from a ...
It's most effective with text files, that's because version control systems are usually built for working with source code.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Holi0317 Thanks for checking the behavior in VSCode. I think we have made a step forward in solving this problem.
BTW, I am the maintainer of
coc-volar
.coc-volar
currently avoids the bug by adjusting the document version when executing code action etc.A workaround? Please.