feat: emulate Firestore read-after-write transactions - #99
Merged
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.
Fixes #98.
Adds the opt-in
dalgo2memory.WithNoReadsAfterWritesInTransaction()mode to emulate Firestore transaction ordering. When selected, reads after the first successful write returnErrReadAfterWriteInTransaction; the default memory-adapter behavior remains permissive.Covers all read and write API variants, and documents the mode as a Firestore-compatible testing aid.
Validated with
go test ./...andCGO_ENABLED=1 go test -race ./....