Closed dragonlipz closed 1 week ago
Latest commit: 85e3dfb28b86a375899e750806e2972330e26b1a
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 | Jun 19, 2024 0:38am |
flowbite-react-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 19, 2024 0:38am |
[!WARNING]
Rate limit exceeded
@SutuSebastian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 50 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 8de012c55d057ab66aa2a33379573d7ee9bad0e7 and 85e3dfb28b86a375899e750806e2972330e26b1a.
The recent updates to the dropdown.mdx
file enhance the documentation for the React Dropdown component. Key changes include clarifications on the component's functionality, usage, and customization options. Notably, it emphasizes the need to disable enableTypeAhead
for more complex headers containing input controls to avoid keystrokes being misinterpreted as item searches. Additionally, the descriptions have been refined for better readability and comprehension.
Files | Change Summary |
---|---|
.../dropdown.mdx |
Added an instruction for setting enableTypeAhead to false when using complex headers with input controls. |
.../dropdown.mdx |
Improved clarity and instructions for the React Dropdown component, including refinements in terminology and examples. |
In the realm of dropdowns, clear and bright,
We crafted changes, shining light,
On usage tips, so true refined,
For inputs mixed with care combined.
A rabbit’s joy, documentation clear,
Dropdowns now, with less to fear!
🐰✨
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?
This is for issue #1341 preventing the use of
<input />
or<TextInput />
controls in the header section of a DropDown.This Does add a new property to the
<DropDown />
component to prevent default behavior of@floating-ui/react's
useTypeAhead
functionality. That, according to@floating-ui/react
documentation, should not be used for typeable elements.New Prop:
DropdownProps.enableTypeAhead?: boolean
default: true
Non-breaking, to existing behavior. When set to false, disables the 'useTypeAhead' functionality.I'm uncertain if this is the desired naming of the property.
disableTypeAhead
seems more appropriate, but then it's negative use may be more confusing for users.Summary by CodeRabbit
enableTypeAhead
to false for complex headers with<input>
or<TextInput>
controls.