[prc5]

Closes #153

Summary

A GraphQL request can now have its own URL path, and setQueryParams() reaches the URL.

const getUser = client.createRequest<{ response: UserResponse; payload: { id: number } }>()({
  endpoint: "/User", // URL path, appended to client.url
  document: USER_QUERY, // string | DocumentNode, sent as `query`
});

getUser.setQueryParams({ source: "app", build: "1.2.3" }).send({ payload: { id: 1 } });
// POST {client.url}/User?source=app&build=1.2.3
// body: { query, variables: { id: 1 } }

• POST: query params are appended to the URL, query and variables stay in the body.
• GET: query params are merged with query and variables, which win on collision (also for forms like query[]=x).
• Mapper: query params go through unstable_queryParamsMapper, which may return a string or an object.
• Without document: endpoint is still the document and the URL is still client.url.

Changes by package

• core: a new trailing Adapter generic lets an adapter declare extra createRequest fields, so document is a type error on other adapters and survives mapper setters. The devtools endpoint getter also receives the request options.
• graphql: URL building, query params, and key mappers.
• testing: createGraphqlMockingServer handles document requests and matches the full path. It would otherwise have thrown on them.
• hyper-flow: passes the request options to the devtools endpoint getter.
• docs: URL path and query params sections in the GraphQL overview.

Decisions to review

1. Keys include the path. The issue asks for the operation name from document. Keys also contain the path (POST_GetUser/User--), because otherwise /v1/User and /v2/User would share cached data. Keys of requests without document are unchanged.
2. Query params also apply without document. The issue says "nothing changes" there, but also lists ignored query params as a limitation. Those requests now go to client.url?source=app, which only affects code already calling setQueryParams().
3. Variables are not inferred from document. ExtractGqlRouteParams is not connected to createRequest today, and a gql document can't be read at the type level. send({ payload }) still needs the payload generic, which the example in the issue leaves out. String documents can use payload: ExtractGqlRouteParams<typeof USER_QUERY>.
4. Wider default query params type. It is now QueryParamsType | string | undefined, so setQueryParams({...}) compiles without declaring queryParams.

Known limitations

• setQueryParamsMapperConfig replaces the defaults, including encoding, so a partial config sends unencoded values. The docs show spreading stringifyDefaultOptions.
• The devtools UI was not opened. The operation name display is covered by unit tests of the getter only.

Test plan

Same steps as CI, run from the repository root with exit codes checked:

• pnpm build
• pnpm lint (run per package, 12 of 12 with exit code 0)
• pnpm typecheck
• pnpm test (firebase and firebase-admin are excluded by the script)
• graphql: 118 tests, 10 runs in a row before the last hyper-flow fix, including E2E against a real HTTP server that checks the path and query string
• Type tests with expectTypeOf and @ts-expect-error

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 9.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀