Skip to content

fix: Add index to Pagination key for uniqueness in starter-example #1038

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

Closed
wants to merge 1 commit into from

Conversation

GoWithFloww
Copy link
Contributor

While following the dashboard tutorial, I identified that the Pagination component in the starter-example uses an incorrect key prop, which could cause potential issues with React's list rendering.

This issue has already been corrected in the final-example code, as seen in PR #640(#640).

This pull request updates the starter-example to use the correct key prop, consistent with the fix in the final code. This ensures learners starting the tutorial won't encounter this discrepancy as they uncomment the code step-by-step.

Copy link

vercel bot commented Apr 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-learn-starter ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2025 6:51am
next-seo-starter ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2025 6:51am

Copy link

vercel bot commented Apr 9, 2025

@GoWithFloww is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

@GoWithFloww GoWithFloww changed the title fix: Add index to Pagination key for uniqueness in stater-example fix: Add index to Pagination key for uniqueness in starter-example Apr 9, 2025
@GoWithFloww GoWithFloww closed this Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant