Open dhavalveera opened 2 months ago
Latest commit: cecd43a031677be81bbe6ac820adafbffbed628e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
flowbite-react | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 8, 2024 8:52am |
flowbite-react-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 8, 2024 8:52am |
[!WARNING]
Rate Limit Exceeded
@dhavalveera has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 3 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 915d52cb106d702e6e7e246ec22afe077b4d352d and cecd43a031677be81bbe6ac820adafbffbed628e.
This update introduces pagination functionality to the <Table>
React component, enhancing its capability to manage and navigate through larger data sets efficiently. Users can now paginate data using either numbered navigation or Prev/Next buttons, improving the component's usability for displaying product information across multiple pages.
Files | Change Summaries |
---|---|
.../docs/components/table.mdx |
Added pagination functionality for <Table> , including number-based and Prev/Next button navigation. |
.../examples/table/index.ts |
Exported pagination functionality. |
.../examples/table/table.pagination.tsx |
Introduced a pagination feature for the table component to navigate through data pages. |
1
when only one page is present.🐰✨
In the realm of code where tables extend,
A rabbit hopped, a feature to amend.
With pages numbered, or buttons to press,
Navigating data, no longer a mess.
📚🔢🐾
So hop along, through data vast,
With pagination, a blast from the past!
🎉🐰
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
on dark theme it has no active item
on dark theme it has no active item
Okay!. I'll check and update it. Thanks for point it out..
@SutuSebastian Sir, one question though it arises in my mind is like, in the current Pagination component, we're limiting the size to 5 without allowing or giving an option to the User, that whether they need to show more or not on the single page by-default. e.g. by-default I want to show 10 rows per Page, but with the current Pagination it's restricted or can say it isn't allowed, then I guess we need to modify the Pagination to allow the User to pass an arbitrary value that how many rows/result they want to show on a single page instead of not allowing them to modify this behavior.
Please share your @SutuSebastian inputs & feedbacks on this, and if this makes a valid point, then I would be happy to go ahead and make this necessary changes.
@dhavalveera totally agreed. Lets fix and extend the pagination component properly and make it production ready once in for all.
The current state is broken.
While u're at it, investigate how a pagination component should work and the flexibility of it, and try to make a controller for it (a hook) and expose that as well, for the headless approach
@dhavalveera totally agreed. Lets fix and extend the pagination component properly and make it production ready once in for all.
The current state is broken.
For this one, I'll dig into the existing Pagination
Component and we check it out how I can extend one to fix it and it production ready.
While u're at it, investigate how a pagination component should work and the flexibility of it, and try to make a controller for it (a hook) and expose that as well, for the headless approach
while working with Table.Pagination
Component I understood a little bit is like we need to provide different kind of Pagination
to the Users as like below:
Next
/ Previous
ButtonNext
/Previous
Button with Numbers in between if they want that as wayLeft
/Right
Icon for Prev/NextPagination
for Numbers with Square
/Circle
as an Border & maybe different colors.those are some possibilities I came across for the Pagination
Components.
Furthermore @SutuSebastian -- above suggestions & possibilities I came across for the Pagination
components aren't implemented in the Flowbite
's Core Package, so how we can proceed it with flowbite-react
?
@SutuSebastian please share your feedback & input on this.
@SutuSebastian - can you please review?
1318
this PR adds the Pagination Component to the Table.
Summary by CodeRabbit
<Table>
component to efficiently manage and navigate through large data sets. Users can now choose between numbered page navigation or Prev/Next buttons for easier data exploration.