feat(tanstack-query-plugin): add agentic features#201
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
V3RON
force-pushed
the
feat/agentic-tanstack-query
branch
from
0d134ed to
3775aef
Compare
# Conflicts: # packages/cli/skills/rozenite-agent/SKILL.md
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.
Description
Adds agent support to
@rozenite/tanstack-query-pluginwith a curated tool surface for inspecting queries and mutations, paginating large caches, managing query cache entries, and clearing query/mutation caches. It also unifies TanStack devtools action handling so UI and agent flows share the same implementation.Context
This follows the agentic patterns already introduced for the Network Activity and Redux DevTools plugins. The exposed tools intentionally mirror the UI's operational capabilities, while excluding UI-local controls. Query and mutation listings use cursor pagination, and detail responses are sanitized to stay JSON-safe for agent consumption.