Closed paghar closed 3 months ago
Latest commit: 8c87f0ec5faf6e0a1af1e93fc25a3cb97b00defe
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 4, 2024 0:37am |
flowbite-react-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 4, 2024 0:37am |
The recent update focuses on standardizing the use of list item components within a specific tsx
file. By transitioning from ListItem
to List.Item
, it ensures consistency and adherence to the component structure, potentially improving readability and maintainability of the code without altering the list items' appearance or functionality.
File Path | Change Summary |
---|---|
.../examples/list/list.advanced.tsx |
Replaced ListItem with List.Item within the List component. |
🐇✨
Changes afoot in the realm of code,
WhereListItem
once freely roamed,
NowList.Item
takes its abode.
In unity, the elements homed,
A rabbit's work, neatly combed.
🌟📜
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?
fix(web) list item in advanced example witch should be "List.Item" in client.tsx.
There are no breaking API changes.
Summary by CodeRabbit
List
component to useList.Item
for list items, ensuring consistency and maintainability.