What agents should know before contributing
TanStack/query
🤖 Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query.
Read by Bluet from 3 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.
Rules its files tell agents (6)
- CONTRIBUTING.md
mustNever let an LLM speak for you - all comments, issues, and PR descriptions should be written in your own words…
Never let an LLM speak for you - all comments, issues, and PR descriptions should be written in your own words, reflecting your own understanding.
- CONTRIBUTING.md
mustNever let an LLM think for you - only submit contributions you fully understand and can explain.
- CONTRIBUTING.md
shouldDo not mass-submit unrelated or low-quality AI-generated pull requests.
Do not mass-submit unrelated or low-quality AI-generated pull requests. We treat that behavior as spam and may close the pull requests, block the contributor, and report the GitHub account.
- CONTRIBUTING.md
shouldDocumentation, CI, examples, and other development-only changes do not require a changeset.
This repo uses Changesets to automate releases. Every change that affects a published package must include a changeset. Run pnpm changeset and commit the generated file. Changeset descriptions are included in the changelog, so make them clear and useful. Documentation, CI, examples, and other development-only changes do not require a changeset.
- CONTRIBUTING.md
shouldDo not run pnpm run test:lib inside individual package folders.
Do not run pnpm run test:lib inside individual package folders. This can cause test failures due to dependencies between packages. Always run tests from the root folder using nx commands.
- CONTRIBUTING.md
shouldDo not submit unreviewed, low-quality, or irrelevant generated code.
You may use AI tools to help generate code, but you remain responsible for understanding, testing, and verifying every submitted change. Do not submit unreviewed, low-quality, or irrelevant generated code.
Decisions its pull requests settled (24)
- #11161clear stale select error when observer switches to a query without data
- #11168consume hydration data client-side via a provider-owned streaming channel
- #11181make the docs link check work on Windows
- #11188avoid prototype property false-positives in no-unstable-deps
- #11249add regression tests for suspense release on programmatic 'setQueryData'
- #11305propagate falsy errors to the error boundary
- #11308rewrite the adapter onto Solid 2.0's native async model
- #11325scope useMutation's cache subscription to the flight
- #11326built-in single-flight consumer via FLIGHT_DATA_SOURCE
- #11360don't re-create and refetch a removed query
- #11366generate reference docs with TypeDoc
- #11378add JSDoc and generate reference docs with TypeDoc
- #11438add JSDoc across the package and expose it in generated reference docs
- #11477add type tests for its batching, scheduling and configuration API
- #11478add type tests for its public surface
- #11483add type tests for 'streamedQuery' parameters and inference
- #11484add type tests for 'TimeoutManager' and its provider types
- #11486add type tests for 'MutationCache', its config and notify events
- #11487add type tests for 'QueryCache', its config, store and notify events
- #11488add type tests for 'createRetryer', its config and retry value types
- #11489add type tests for 'dehydrate', 'hydrate' and the dehydrated state types
- #11491add type tests for 'MutationObserver' and its result branches
- #11528match only the subject in the autofix commit guard
- #11572remove dead 'QueriesObserver' type tests duplicated by 'query-core'