Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pagination - Ability to disable navigation arrows based on custom conditions #10312

Closed
jpuzz0 opened this issue Apr 29, 2024 · 3 comments
Closed

Comments

@jpuzz0
Copy link
Contributor

jpuzz0 commented Apr 29, 2024

Is this a new component or an extension of an existing one?
Existing - Pagination -> Navigation

Describe the feature
Ability to pass navigation props or an entirely custom Navigation component to the Pagination component that would allow users to disable forward and backward navigation icons based on a custom condition.

There is a use-case with a specific API/set of data in Openshift AI where no combination of itemCount & perPage gives us our desired behavior.

Any other information?
In the interim, we're currently adding/removing the disabled attribute for the "Next" pagination's navigation icon in a react effect by way of a querySelector.

@jpuzz0 jpuzz0 added the Feature label Apr 29, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in PatternFly Issues Apr 29, 2024
@tlabaj tlabaj added the md label May 2, 2024
@tlabaj tlabaj moved this from Needs triage to Backlog in PatternFly Issues May 2, 2024
@tlabaj tlabaj added this to the Prioritized Backlog milestone May 2, 2024
Copy link

github-actions bot commented Jul 8, 2024

This issue has been automatically marked as stale because it has not had recent activity.

@github-actions github-actions bot added the Stale label Jul 8, 2024
Copy link

github-actions bot commented Sep 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Copy link

This issue has been closed because it has not had activity since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in PatternFly Issues Sep 21, 2024
@tlabaj tlabaj removed this from the Prioritized Backlog milestone Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants