feat(sanity): use optimistic locking when publishing documents

sanity-io · May 17, 2024 · cf97baa · cf97baa
1 parent 435ae19
commit cf97baa
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/packages/sanity/src/core/store/_legacy/document/document-pair/serverOperations/publish.ts b/packages/sanity/src/core/store/_legacy/document/document-pair/serverOperations/publish.ts
@@ -32,6 +32,12 @@ export const publish: OperationImpl<[], DisabledReason> = {
  actionType: 'sanity.action.document.publish',
  draftId: idPair.draftId,
  publishedId: idPair.publishedId,
+ // The editor must be able to see the latest state of both the draft document they are
+ // publishing, and the published document they are choosing to replace. Optimistic
+ // locking using `ifDraftRevisionId` and `ifPublishedRevisionId` ensures the client and
+ // server are synchronised.
+ ifDraftRevisionId: snapshots.draft._rev,
+ ifPublishedRevisionId: snapshots.published?._rev,
  },
  ],
  },