Skip to content

fix: batched changes #428

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

Merged
merged 3 commits into from
Jun 16, 2025
Merged

fix: batched changes #428

merged 3 commits into from
Jun 16, 2025

Conversation

psteinroe
Copy link
Collaborator

this should finally fix batched changes.

i was super confused every time i worked on this because it seemed like whatever i did, somehow something did not work. Turns out, we cannot rely on lsp clients to send batched changes consistently. this now fixes it by

  1. sorting changes starting with the last
  2. applying them starting from the last
  3. not changing the ranges in any way

had to delete another test that has faulty data, but i am very sure that the three test cases cover both neovim and vscode behavior.

will push out a patch release once this is merged and hope the reports are not popping up again.

Copy link
Collaborator

@juleswritescode juleswritescode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice! seems simpler, too :)

@juleswritescode juleswritescode changed the title fix: batched changess fix: batched changes Jun 16, 2025
@juleswritescode juleswritescode merged commit 31e6ddf into main Jun 16, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants