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
Why are there so many APIs which have a WithPatches suffix. Would it for example not enough to have one merge which returns [Patche] by default. Has this some performance reasons?
Generating patches changes the way that automerge processes operations, for example if we're generating patches then when a key is deleted we need to figure out if the deletion of the operation in question exposes any concurrent values which were hidden by the deleted key and then we have to generate patches which represent the creation of the exposed value. The performance impact can be large enough on large document histories that I don't think we should deny the user the option to choose whether to generate patches.
Why are there so many APIs which have a WithPatches suffix. Would it for example not enough to have one merge which returns [Patche] by default. Has this some performance reasons?
Example:
The text was updated successfully, but these errors were encountered: