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
Commits are atomic changes to a resource. If these are persisted, we can use these to generate logs and previous versions. Pretty cool.
I think it makes sense to simply store these as resources (since they are just that) - not as some special struct.
One thing I'm still pondering about, is how to deal with failed commits. For now, if a commit cannot be applied, it will not be stored. This works fine for synchronous APIs (e.g. posting a Commit to a /commit endpoint), but this would not work when these commits are sent in bulk.
Commits are atomic changes to a resource. If these are persisted, we can use these to generate logs and previous versions. Pretty cool.
I think it makes sense to simply store these as resources (since they are just that) - not as some special struct.
One thing I'm still pondering about, is how to deal with failed commits. For now, if a commit cannot be applied, it will not be stored. This works fine for synchronous APIs (e.g. posting a Commit to a
/commit
endpoint), but this would not work when these commits are sent in bulk.store.commit()
)For the future:
The text was updated successfully, but these errors were encountered: