-
Notifications
You must be signed in to change notification settings - Fork 642
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
Allow to clear <select> field #161
Labels
Milestone
Comments
wojtek-krysiak
added a commit
that referenced
this issue
Aug 26, 2020
🎉 This issue has been resolved in version 3.1.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Merged
github-actions bot
pushed a commit
that referenced
this issue
Aug 27, 2020
# [3.1.0](v3.0.1...v3.1.0) (2020-08-27) ### Bug Fixes * disabled fields are stripped from the payloadrelates to [#430](#430) ([f0b4319](f0b4319)) * make sure old adapters also work ([cb0bd3f](cb0bd3f)) * onChange can also update other fields ([46dacb9](46dacb9)) * propert handle null valuescloses [#304](#304) ([7d16a4e](7d16a4e)) ### Features * allow to clear <select> field ([19e8db9](19e8db9)), closes [#161](#161) * release ([d21ec77](d21ec77)) * unify flatten unflatten logic ([b8435de](b8435de)), closes [#352](#352)
🎉 This issue has been resolved in version 3.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When there is a select field (i.e. reference) there should be an option to clear it's value (when field is not required)
In this task it would be perfect if we can rewrite the select component to be in our design system
The text was updated successfully, but these errors were encountered: