Skip to content

fix: canNavigate check in goToPage reducer #2805

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

Merged
merged 1 commit into from
Oct 26, 2020

Conversation

schoettker
Copy link
Contributor

Since the pageIndex is zero based it has to be less than pageCount
for canNavigate to be true. If pageIndex is equal to pageCount,
canNavigate should be false, otherwise a non-existing page would be accessed.

Since the pageIndex is zero based it has to be less than pageCount
for canNavigate to be true. If pageIndex is equal to pageCount,
canNavigate should be false, otherwise a non-existing page would be accessed.
@vercel
Copy link

vercel bot commented Oct 26, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/tannerlinsley/react-table/6s9ejffvg
✅ Preview: https://react-table-git-master.tannerlinsley.vercel.app

@tannerlinsley
Copy link
Collaborator

🎉 This PR is included in version 7.6.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants