Thanks for the reply @trisolaran
I don’t have much experience with Bootstrap. I’ve tried, but I haven’t created anything nice yet and I’m pressed for time 
, if I still manage to create something I’m at least partially satisfied with, I’ll be happy to share it with the community. 
Changes:
phx-focus and phx-blur options. You can use these options to specify events to be sent to the parent LiveView/LiveComponent when the text input receives or loses focus. See the cheatsheet for a couple usage examples.live_select_change event is now sent directly from the JS hook instead of playing ping-pong between client and server. This saves a round-trip and should reduce response times.field assign of type Phoenix.HTML.FormField instead of separate form and field assigns (which is still supported but soft-deprecated with a warning)Thanks to all who provided feedback!
Hi Max, have been out of action for the past 8 months .. just picking back up.
There have been significant changes that I am catching up to in phoenix etc. Amazing how fast this ecosystem is moving (unfortunately, I have a lot of work to do on refactoring for updates/changes).
One of the things I am trying to figure out in the latest live_select are how to get certain behaviors working again .. specifically - I was using multiple live_select components on a form that were “linked” i.e. the values returned were conditional upon the values of the other components eg. category & sub_category etc.
Am trying to figure out how this is handled in the final design .. in the “live_select_change” event, I am seeing the field attribute populated with the form-name+field_name, which is a bit weird, how do I access the other live_select component values on the form from the triggered handle_event etc.
Any pointers ?
Thanks in advance ..
Hi @milangupta . It’s hard for me to help without seeing any code. Sharing a minimal example with a precise description of what you’re trying to achieve would be great. Cheers.
Great library, thanks for open sourcing this. I see that one of the arguments for live_select component is options and would be my choice to populate current tags that belong to a resource I am editing, however, this argument can’t be overridden in case there is a new search and selection.
The library works fine for me for searching and adding tags to a resource but what about editing current tags? What do you suggest for edit forms?
Thanks
Thanks @pedroassumpcao ,
Yes it can the options assign in the component can be set in the template but can be overridden anytime
by calling: send_update(LiveSelect.Component, id: live_select_id, options: new_options)
that’s what the live_select_change event is for.
Thanks for the reply, but I made a mistake in my question, I was talking about pre-populating the selected options and I tried using values what works fine for that, however, once value is set, it seems any other search and selection can’t be done.
Imagine the scenario where I have a resource that has multiple tags and I wanna edit them. I can pre-populate the current tags in value but I can’t add a new tag (or remove existing ones).
This is how all input elements in Phoenix.HTML.Form (or core components) work: if you set value explicitly, then that value is used.
If you don’t set it however, the current value of the input will be taken from the form.
LiveSelect is no different: make sure that the form is initialized with your resource, and live select will pick up the value from the form.
I got it working, in my form component update/2 I send an update to live select component send_update(LiveSelect.Component, id: "live_select_component_id", value: current_tags). The current tags are defined and passed to my form component that utilizes live select component. This way, live select component value does not need to be set and current tags can be removed, or new tags can be searched and added.
I would expect that setting value in live_select would perform the same way I am doing through an explicit send_update but it does not, as it seems the value set always overrides any change in the selection.
You’re over complicating it see my previous response. Treat it as any other input.
You shouldn’t need to set value at all in your scenario AFAICS