-
Notifications
You must be signed in to change notification settings - Fork 452
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
SelectBox is missing the props required and name #366
Comments
Good points, we'll try to add these props! |
@mitrotasios can u give some guidance in where to start? I can add those |
hey @jorgeramirezamora thanks for offering this, we are currently working on migrating our Input elements to use headlessui as it would enable us to make them easily accessible. So I think it wouldn't make sense to start working on this issue until the migration is complete. Should I get back to you once this is the case? Also, feel free to join our Slack community and we can chat about delegating other tasks to you if you're interested in contributing! |
Makes sense. And yes please, I am interested in contributing 🚀 How can I join Tremor's Slack? |
Awesome! Here’s the link: https://t.co/g99pltTvIC |
Hey @jorgeramirezamora, the select boxes now run on Headless UI and we still need to add |
Sure, lemme wrap up #670 first |
@jorgeramirezamora awesome, thanks! |
I would like to be assigned for this. :) |
I am using SelectBox and MultiSelectBox in a form and here I dont have props like |
There is already a PR (#729) on this |
🎉 This issue has been resolved in version 3.13.2-beta-select.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.13.4-beta-select.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.13.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I'm using the standard HTML form element so it would be nice to have the
name
property to handle form data on submit.SelectBox it's also missing the
required
property.The text was updated successfully, but these errors were encountered: