Repository navigation
Restore direct tracking links without intermediate provider choice - #25
Merged
Merged
Conversation
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
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.
Compared the original orders.edge.app UUID search interaction: results expose direct destination links. Restore that behavior for all candidate results; the link click is the explicit provider choice. Collapse optional provider filter and simplify copy/status noise. Preserve candidate uncertainty in API metadata and concise UI copy; no auto-navigation or upstream requests. Full npm run check passes (101 tests, build, links, Worker dry-runs, secret scan). Local browser preview was blocked by browser navigation policy; verify live Swapuz, ambiguous UUID, mobile and unknown/provider-filter flows after rollout.