-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
Feature Request: Custom options for select field #78
Comments
You can pass allowedValues as property to the select-field and add a transform-function that returns a label for each value to achieve the same thing. In my case i created custom form elements where i declare an options-property, which is an array of {key, value} like in autoform because that is much easier to implement than allowedValues and transform. |
I see your point. But wouldn't it be easier and more simple to bake it directly into the library? |
The options property works great! |
For the validator there is still a empty string and so my validation fails. |
Well, I have to think about it. Also, it would be nice, @RSchwan, if you could describe your desired API (and behaviour) here. |
Ok I figured out where my problem was. I didn't know that custom validations are fired although I you have optional set to true. |
It's good to know it, thanks. |
See http://autoform.meteorapp.com/select
This would allow dynamic select fields
The text was updated successfully, but these errors were encountered: