patternfly / patternfly/react-data-view
Odd interaction between filtering and pagination
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I noticed this when applying Data view in OpenShift console.
If a filter is applied to a table that is not on a page that includes the row or rows resulting from the filter, the pagination forward/back controls are disabled, the pagination count shows an inaccurate count, and the table displays no results. Changing the pagination count to a higher value resolves the bug.
https://github.com/user-attachments/assets/3cae33d3-d322-4989-a92d-ccac671dc295
See https://codesandbox.io/p/devbox/icy-feather-d39zd2?workspaceId=ws_E3FWuNWwfWsX1UNyq5bcoF and https://d39zd2.csb.app/?name=admin
Jira Issue: PF-2649
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the linked CodeSandbox reproduction and compare the table behavior before and after changing the pagination size. Then trace the filtering and pagination entry points in the react-data-view repository; done means filtered rows appear correctly, pagination controls and counts reflect the filtered result set, and the regression is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100