Keep Orders map selection across pages - #200
Merged
Merged
Conversation
Constraint: Orders load in server pages of 50 while route drafts need one combined selection. Rejected: Per-page Add to map | repeats the operator action and discards off-page intent Confidence: high Scope-risk: narrow Directive: Clear manual selection on filter-scope changes, not page navigation. Tested: 494 app tests; 110 targeted tests; lint; production build; typecheck; public URL guard. Not-tested: Embedded K-food browser interaction; standalone Polaris snippet validation stopped after three harness-level failures.
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.
Why
Orders are server-paginated in groups of 50, but manual selection was derived only from the currently visible page. Operators therefore had to add each page to the map separately.
What changed
Verification