Maharshi Alpesh
Maharshi Alpesh
@jrgarciadev sure, will do!
* Made the changes to make input similar to select in case of flat variant. * Updated the example in PR description.
@coderabbitai full review
Applied the comments in [a168061](https://github.com/nextui-org/nextui/commit/a1680612a43420a2597ee92f3c627fa2aac052f1). Will add the documentation as well. Also talking about keyboard left/right navigation, I thought it would be nice UX that whenever a user selects the...
Comments are addressed(a1680612a43420a2597ee92f3c627fa2aac052f1) and docs are added(bc5286c076e6088f7a5e4a86136c177651ea10d3) The PR is ready for the next round of review. @wingkwong, can you please have look at the PR again?
Added the suggestions mentioned in [comment](https://github.com/nextui-org/nextui/pull/3748#pullrequestreview-2334880072) in https://github.com/nextui-org/nextui/commit/cab6a940e04a8e4d75fd89529b1dafb6bbc33a5c Just one concern regarding following suggestion: - in Required, the error message the field is required only shows when there is no...
The current input-otp component handles the validation behaviour similar to input component. We can configure the error-message by `errorMessage` prop, so did I miss anything as you mentioned `should be...
@coderabbitai pause
Hi @ryo-manba, The current code uses the vanilla radio inputs which suffices the need of the rating component. Reference from rating-segment component: ``` ``` Just trying to understand more, why...
@coderabbitai pause