Drafts

[a-type]

A draft should be splittable from any entity. It should conform to the exact same API and be usable in the same way, except it doesn't affect the original and isn't synchronized until committed.

Once committed, any accumulated changes within the draft are added as one batched change set to the original entity/ies.

Use case: forms where changes should not be immediately applied to synced data. An alternative API to use batching.