Keep prescription pagination isolated during search changes - #329
Draft
evangauer wants to merge 1 commit into
Draft
Keep prescription pagination isolated during search changes#329evangauer wants to merge 1 commit into
evangauer wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
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.
Reopening the prescription inventory picker immediately after selecting a search result can let a scroll event append the previous search page to the reset catalog. This mixes results and skips the beginning of the next page. Pagination now advances only while the picker is open, the search is settled, and the query is neither failed nor fetching.
Verified the same component change in an isolated release-base checkout: reproduced the mixed 70/125 result, then confirmed retry restores the correct 50/125 result after the fix; checked duplicate names, SKU selection and a 390px mobile viewport. The four targeted suites pass (56 tests), and the production build passes. The rendered fixture uses synthetic tRPC data; authenticated application verification remains outstanding.
GitHub CI also passes on this main-based PR: build/type checks/tests, migration history, RLS tenant isolation and CodeQL. Hosted preview builds were skipped by the existing build policy and do not count as browser verification.
Tracks OPENVPM-92. No schema or dependency changes.