You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The merging parser is responsible for deserialization. We would need to create a serializer that is able to preserve merge keys. But that is somewhat difficult to handle.
Given the little time I have to dedicate to this project, I barely sqeezed through the holidays this pr:
Activity
gabriel-samfira commentedon Jan 5, 2026
Hi @camitz
The merging parser is responsible for deserialization. We would need to create a serializer that is able to preserve merge keys. But that is somewhat difficult to handle.
Given the little time I have to dedicate to this project, I barely sqeezed through the holidays this pr:
which adds round-trip support for most cases (not merge keys/anchors though).
So I make no promises for as to when this will ever be added. If you do have time to help with this, it would be amazing.