feat(client): add conditional record operations - #5
Draft
rrrodzilla wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional RecordRevisionClient facet from createForgeClient with fresh versioned reads and conditional PATCH, PUT and DELETE. Existing ForgeClient implementations remain compatible.
Each mutation checks a fresh authorized baseline before sending If-Entity-Revision, so an older or unprepared backend receives no mutation. Changed account/program context, stale revisions and failed responses are surfaced without automatic mutation retries. Documentation distinguishes the preflight from the backend's atomic protection and explains uncertain outcomes.
Validation: 20 built-client tests pass, including existing file access cases, unsupported backends, context changes, conflicts, cancellation and lost mutation responses. Client/React/console/Storybook builds and type checks pass. Existing Storybook tooling/chunk warnings remain. Minor changeset included; no registry release.
Stacked on the file-client branch from #4. Backend protocol implementation is being prepared in Govcraft/schemaforge; live consumer adoption is a separate verification step.