feat(ui): show where a pasted identifier leads, above corpus results - #9679
Open
JSONbored wants to merge 1 commit into
Open
feat(ui): show where a pasted identifier leads, above corpus results#9679JSONbored wants to merge 1 commit into
JSONbored wants to merge 1 commit into
Conversation
Closes #9674. The search box called semantic search only and rendered every hit as a link to /subnets/$netuid. Pasting a block hash returned registry results or nothing -- while blocks-ref-page, extrinsics-hash-page and accounts-ss58-page existed the whole time. #9672 shipped the route; this is what makes it visible. ## Alongside, not instead Both queries run on submit. Resolve is deterministic and needs no AI binding; semantic needs both. So a 503 from the AI path leaves the identifier matches intact -- which is the whole reason they resolve separately. ## Above, and not exclusive A user who pasted a hash is not looking for a subnet whose description happens to score well, so matches come first. They do NOT replace the corpus results: `exact` is a claim about SHAPE, not existence -- the route looks nothing up, so a well-formed hash for a block that does not exist still resolves. Keeping the corpus visible means that case degrades to "here is what else matched" rather than a dead end. ## Two candidates read as a question The heading is "Could be" when the query is ambiguous and "Go to" when it is not. A 64-hex string is a block hash OR an extrinsic hash; 7 is a netuid AND a block height. Both are offered rather than guessed. Values are shortened in the MIDDLE. The ends are what a user recognises in a hash or an address, and truncating the tail makes two different hashes look identical. - apps/ui suite 1,851 tests green, tsc clean
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
metagraphed-ui | 85963f9 | Aug 06 2026, 12:37 PM |
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.
Closes #9674.
The search box called semantic search only and rendered every hit as a link to
/subnets/$netuid. Pasting a block hash returned registry results or nothing — whileblocks-ref-page,extrinsics-hash-pageandaccounts-ss58-pageexisted the whole time. #9672 shipped the route; this is what makes it visible.Alongside, not instead
Both queries run on submit. Resolve is deterministic and needs no AI binding; semantic needs both. A 503 from the AI path leaves the identifier matches intact — which is the whole reason they resolve separately.
Above, and not exclusive
A user who pasted a hash is not looking for a subnet whose description happens to score well, so matches come first.
They do not replace the corpus results.
exactis a claim about shape, not existence — the route looks nothing up, so a well-formed hash for a block that does not exist still resolves. Keeping the corpus visible means that case degrades to "here is what else matched" rather than a dead end.Two candidates read as a question
The heading is "Could be" when the query is ambiguous and "Go to" when it is not. A 64-hex string is a block hash or an extrinsic hash;
7is a netuid and a block height. Both are offered rather than guessed.Values are shortened in the middle — the ends are what a user recognises in a hash or an address, and truncating the tail makes two different hashes look identical.
Verification
apps/uisuite: 1,851 tests green;tsccleanlintandformat:checkcleanNo screenshot table — confirmed with the maintainer that this repo does not require one.