BugFix: Handling multiple changes in a singular transaction #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When utilizing codemirror shortcuts such as alt+upArrow to move entire lines or editing via multiple cursors at once, a singular codemirror transaction may contain multiple changes in its change set, causing multiple
am.splice
calls.This causes 2 issues:
am.splice
modifies the provided path variable, causing it to be corrupted on subsequent iterationsfromB
instead offromA
, as it, unlikefromA
, accounts for these index changes. Otherwise aRangeError
may be thrown.