feat(send): prevent duplicate transfer submissions across retries and navigation - #294
Closed
woahwhattheheck wants to merge 2 commits into
Closed
woahwhattheheck wants to merge 2 commits into
woahwhattheheck wants to merge 2 commits into
Conversation
Bind an idempotency key to the exact transfer payload, persist only a safe operation reference in sessionStorage, and return the prior transfer on repeated submits with the same key. Refresh restores in-flight status; an edited payload mintes a new intent. Closes RemitFlow#277
Prevent duplicate transfer submissions across double-clicks, retries, refresh, and navigation by persisting a safe operation reference and reconciling in-flight intents without auto-resubmitting.
Author
|
Superseded by latch/remitflow-277-idempotent-send with stronger timeout/navigation coverage and corrected operation lifecycle statuses. |
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.
Closes #277
Binds a canonical request fingerprint and idempotency key to the exact transfer payload so one user intent creates at most one transfer.
Design
fingerprintTransferPayload+idempotencyKeyForderive a stable key from the transferable fields.sessionStorage.createTransferreturns the prior record when the same idempotency key is replayed.Tests
Compatibility
idempotencyKeyis optional on the Transfer contract for legacy records.