feat(web): delete tracked queries from the dashboard#680
Merged
Conversation
Queries were add-only in the SPA even though DELETE /queries, the `canonry query remove` CLI, and the canonry_queries_remove MCP tool already shipped. The project page's "+ Add queries" affordance becomes a "Manage queries" panel that lists every tracked query with an inline Remove button (delete -> refetch -> error toast), backed by a new removeQueries() wrapper over the generated SDK. Adds a wrapper contract test and bumps to 4.70.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Queries were add-only in the dashboard even though the
DELETE /queriesendpoint, thecanonry query removeCLI, and thecanonry_queries_removeMCP tool already shipped — this wires that existing capability into the SPA.removeQueries()wrapper over the generated SDK (no raw fetch); the manage list reuses the same evidence-derived query set as the existing "N queries tracked" count, so they never diverge.