Closed miguelangel-dev closed 2 weeks ago
Thanks @miguelangel-dev, I'll take a look in depth a little later today or tomorrow, WWDC is dominating my attention right now. In the meantime, Marks has some underlying changes that we should get in before dropping this in place - some API updates that align to the latest core library that I have in some commits in the WIP Blocks PR (#171). I'll pull those out of the existing PR and get those set up so we can merge them without waiting for the full detail work on the Blocks API
@miguelangel-dev I don't think there'll be a serious conflict, but go ahead and rebase over the #171 merge, and things should be good. Biggest detail change here was the internal API switching from Value to ScalarValue inside marks, which I wanted to get in if we were expanding the marks API with these bits.
@miguelangel-dev I don't think there'll be a serious conflict, but go ahead and rebase over the #171 merge, and things should be good. Biggest detail change here was the internal API switching from Value to ScalarValue inside marks, which I wanted to get in if we were expanding the marks API with these bits.
Thanks for moving and merging. I have rebased it against #171 - it should be ready to review 🙏🏻
Thanks both for the code review, I have addressed all your suggestions. It is ready for a second round 🙏🏻
Sorry, added a latest minor change to revert an unnecessary public accessibility into the cursor c6798ffe4a6dacb43abe8ee6576c60345138c7eb
Bindings for being able to retrieve the marks of a given position without traversing the ops of the full document.
187
https://automerge.org/automerge/automerge/struct.Automerge.html#method.get_marks