feat(ui): add the search-resolve query and types - #9675
Merged
Conversation
Part of #9674, ahead of the component change. #9672 shipped GET /api/v1/search/resolve. This adds the client half -- searchResolveQuery plus the ResolvedIdentifier / SearchResolveResponse types -- without touching a component, so it goes through the normal gate instead of being held for manual review alongside a visual diff. ## staleTime: Infinity, which nothing else here uses The answer is a PURE FUNCTION of the query: the same string resolves to the same destinations forever, and nothing on the server can change it. Any finite staleTime would re-request an answer that cannot have moved. ## Deliberately separate from semanticSearchQuery They are independent, and meant to run side by side. Resolve is deterministic and needs no AI binding; semantic needs both. An explorer's most common search must never wait on -- or fail because of -- the embedding path. - apps/ui lib tests: 142 files / 1,146 passed
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
metagraphed-ui | 01e1c4d | Aug 06 2026, 12:00 PM |
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
The previous commit added the import but not the tests -- a failed `cd` in the same command swallowed the append, leaving an unused import that tsc flagged. Written in this file's `expect` style rather than node:assert, and the query-key assertion carries the real shape: `k()` namespaces and network-scopes every key, which matters here because this route is in LIVE_CHAIN_ROUTE_PATHS and answers on testnet too.
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.
Part of #9674, ahead of the component change.
#9672 shipped
GET /api/v1/search/resolve. This adds the client half —searchResolveQueryplus theResolvedIdentifier/SearchResolveResponsetypes — without touching a component, so it goes through the normal gate rather than being held for manual review alongside a visual diff.staleTime: Infinity, which nothing else here usesThe answer is a pure function of the query: the same string resolves to the same destinations forever, and nothing on the server can change it. Any finite
staleTimewould re-request an answer that cannot have moved.Deliberately separate from
semanticSearchQueryThey are independent and meant to run side by side. Resolve is deterministic and needs no AI binding; semantic needs both. An explorer's most common search must never wait on — or fail because of — the embedding path.
Verification
apps/uilib tests: 142 files / 1,146 passedk()builds it), that it never fires on whitespace, and thestaleTime: Infinityrationaleapps/uitypecheck: 0 errorsA correction to an earlier revision of this description
I first described four
apps/uitype errors as pre-existing. They were not defects at all —apps/uitypechecks against@jsonbored/metagraphedand@jsonbored/ui-kit, and neither workspace had been built in this worktree, soApiSchema<"PartnershipMetadata">and friends resolved against absent declarations. Building both clears all of them. Nothing in the codebase needed fixing; my checkout did.The component wiring — and the decisions already settled for it — is #9674.