Repository navigation
fix(api): include Idempotency-Key in apiRequest deduplication key (Fixes #869) - #955
Open
Lion4467cat wants to merge 1 commit into
Open
Lion4467cat wants to merge 1 commit into
Lion4467cat wants to merge 1 commit into
Conversation
|
@Lion4467cat is attempting to deploy a commit to the chonilius' projects Team on Vercel. A member of the Team first needs to authorize it. |
Lion4467cat
force-pushed
the
fix/issue-869-idempotency-dedup
branch
from
November 14, 2026 10:40
7b8aa88 to
b0f3e59
Compare
This branch has not been deployed
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
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 #869
What changed
getIdempotencyKeyHeader(headers?: HeadersInit)insrc/lib/api.ts(handling plain header objects,Headersinstances, and header entry tuples case-insensitively) and included the extractedIdempotency-KeyinrequestKey(...).src/lib/api.test.tsverifying that concurrentapiPost/apiRequestcalls with distinctIdempotency-Keyheaders execute as separate requests while identical keys still coalesce, includingHeadersand tuple-array forms (strictly typed undernoUncheckedIndexedAccess).src/lib/api.tsandsrc/lib/utils.tsso the test suite and linter execute cleanly.Why
apiRequestpreviously deduplicated in-flight requests solely bymethod + path + body, ignoring theIdempotency-Keyheader attached byapiPost. Two claim or funding requests with identical{}bodies and rotated idempotency keys coalesced into the first promise, preventing the rotated key from ever reaching the backend.How to test
npx jest src/lib/api.test.ts --no-coverage(8 passed, 8 total)npx eslint src/lib/api.ts src/lib/api.test.ts src/lib/utils.ts(0 errors, 0 warnings)