-
Notifications
You must be signed in to change notification settings - Fork 569
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
add multiple option for select #526
base: master
Are you sure you want to change the base?
Conversation
when option "multiple" is true, will process original value as array (joined on comma for now for display), and then pass array of selected options directly back to controller. Always adds a button because the change event is often fired spuriously when interacting with a multiselect.
getting an unrelated failure on "should be able to use bip_bool to change a boolean value using an image" locally on master, and now on CI as well. Not sure what is going on with that, will look into if I get a sec |
the block for Combustion.initialize! sets the old values for the test env that turn off digests, so the matcher for the image tag in "should be able to use bip_bool to change a boolean value using an image" works. also moving css files to standard application.css manifest avoids the complaints from rails about "Asset was not declared to be precompiled in production." for each of these.
This is great, although I'm getting |
@EmmaB good catch - I made a commit to deal with that, does it work better? |
@sbeam Sorry for the slow reply -- yes, that works perfectly. |
when option "multiple" is true, will process original value as array
(joined on comma for now for display), and then pass array of selected
options directly back to controller. Always adds a button because the
change event is often fired spuriously when interacting with a
multiselect.
(there seems to be desire for this feature (eg, #285) and it's working in production for me. Feedback welcome - PS this gem is great 👍 )