Add QUERY HTTP method support#27
Merged
Merged
Conversation
ejsmith
marked this pull request as ready for review
July 16, 2026 04:27
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.
Summary
Why
RFC 10008 defines QUERY as a safe, idempotent, cacheable method with request content. FetchClient should support it with the same typed response, middleware, explicit caching, retry, and testing capabilities as its existing methods.
The retry middleware now preserves body-bearing requests across attempts so a QUERY request can be retried without reusing a consumed body stream.
Validation
deno task checkdeno task lintdeno task format-checkdeno task test(196 passed)deno task build --set-version 0.0.0 --allow-dirty