This PR enables single-range moves in Y.Arrays. The data structure is forwards compatible. That means that v14 can read v13 updates, but v13 can't read v14 updates (if content has ever been moved).
The feature is stable. I plan to do a couple of breaking API changes before I make a final v14 release.
Planned changes:
- Remove apis that use the DOM (e.g. toDOM)
- Fix
yxml.toString() - Use 53 bit clientIds by default
- Fix event-path #336
- Simplify event API and remove unused fields
- rename to ListCursor a3b97d9
- extend move info field by three bits for future usage efcfe4b
- remove todo comment 4de3c00
- cleanup 100e436
- Fixed all tests - full support for collapsed move deletions 3b31764
- fix several issues of supporting deleted move ops 1972367
- remove old move-ranges if collapsed 0ce4059
- optimize encoding of move ops 4078e11
- normalize ranges ab5061c
- fix move-range tests of moved-moved items 44499cb
- lint b63d22e
- fix all tests for range-moves of length 1 bf05061
- filter empty ranges when calculating minMoveRanges 7e9319f
- use uint8 type encoding for relative-positions 2e9a7df
- fix a bunch of issues with range-move approach 1f99e82
- implement solid move-range approach - tests not running 69b7f4b
- tmp commit b2b7b8c
- fix test-move logic a0c9235
- fix circlic move-loops e8ecc8f
- fix all remaining bugs for single-item moves (mainly event bugs) b32f88c
- fix search marker issues - splitting of items with stored rel search markers 51c095e
- fix edge case when moving backwards from move operation 285dc79
- fix ListIterator backwards iteration within moved ranges f65d1b8
- fix prevMove bug c4b28ac