feat(database): owner filter and pagination for models list#281
Open
JohnChantz wants to merge 1 commit into
Open
feat(database): owner filter and pagination for models list#281JohnChantz wants to merge 1 commit into
JohnChantz wants to merge 1 commit into
Conversation
Add owner-chip filtering and server-side pagination (limit 10) to the Database Models list. Search, selected owners, and current page are all driven by URL search params (?search, ?owner, ?page), so filter state is shareable, survives reload, and works with browser Back/Forward.
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.
Add owner-chip filtering and server-side pagination (limit 10) to the Database Models list. Search, selected owners, and current page are all driven by URL search params (?search, ?owner, ?page), so filter state is shareable, survives reload, and works with browser Back/Forward.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
masterbranchfix #xxx, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: