mirror of
https://github.com/vitorpamplona/amethyst.git
synced 2026-10-06 03:38:23 +00:00
Claude
1f72b3c080
`directRouteResolver` auto-navigated on any nip19 code found *anywhere* in the box. `Nip19Parser` extracts a code from inside a string, which is right for spotting a mention in a note and wrong for reading a search field — so once `from:`/`to:` existed, typing `from:npub1…` looked exactly like pasting a profile and threw the reader onto that person's page halfway through writing a filter. The profile/post auto-navigation is gone. Invite links stay: they cannot be typed by accident (both need a URL carrying `/invite/`, which no token produces) and they open a redeem flow rather than a profile or a post. Deleting it alone would have regressed pasting, though — the old code read "navigate on hit without displaying results", so the jump *was* the only path to a pasted code, and a paste of somebody the cache had never seen would have surfaced nothing at all. A whole-input code now resolves into the results list instead: consumed into the cache and offered as an ordinary user or note row. Still one tap away, but the reader chooses when to leave. `wholeInputNip19` in commons is the rule that separates the two cases — a paste is the only thing in the box, a token always carries its prefix. Desktop's `parseSearchInput` had the same extract-from-anywhere behaviour and now goes through it too, so a `from:` filter no longer produces a direct-lookup row for somebody the reader was merely filtering by. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017yKjw2WqwZpSzsqcYZMnkV