Hello all! I’ve been working a few days on trying to solve a relatively simple issue, however it’s turning into quite the road block. I have a Live Component. which is nested inside of a Form Component which I’ve used to replace a custom AJAX search box which was dreadful to use and consisted of 40…

[image] dakora: That won’t work because calling update wipes out all of the existing assigns for the component, and there is no way to get the originals back to it (as its a different component thats requesting the update). This shouldn’t be true, are you using stateless or stateful component…

I usually have a simple public API for each component that needs to be talked to. Something like: defmodule LiveComponentTwo do ######### Public API def update_text(id, text) do send_update(__MODULE__, id: id, update: :update_text, text: text) end ######### def update(%{update: :upda…

If i’m understanding the differentiation in the docs I believe they are stateful. I use handle_event all over them and they are Phoenix.LiveComponent’s and not Phoenix.Component’s. My update function looks like this: def update(assigns, socket) do name = String.to_existing_atom("#{Map.get(assig…

I did try pattern matching like that however I ran into the same issue where it wiped out all of my assigns.

Here’s the Live Component in question. Note that it’s a prototype and employs thousands of dirty, no good hacky hacks. defmodule Proj.Search do use Phoenix.LiveComponent use Phoenix.HTML import Ecto.Query alias Proj.Repo @impl true def update(assigns, socket) do name = String.to_…

Right I guess what I was trying to look for was a version of the pattern matching on update that wasn’t working as you expected. The version you’ve posted here has a single def update clause.

Well now that i’ve gone back and combed over the multiple update defs method it’s working for me! It sure would be nice if this behaviour was documented… Thank you for pointing me in the right direction

Thank you SO much for posting this example! I just ran into the same issue when trying to communicate between components and this is incredibly helpful. I had not thought of writing two update functions and then pattern matching on a specific update. Quick question … If I’m understanding your app…

It’s cleaner this way, easier to refactor, it’s obvious that this component is called from outside just by opening the file.

Communicating Between Live Components

Questions & Help Questions

benwilson512 December 28, 2021, 7:05pm 6

Can you show an example? I have lots of code that works this way and it works just fine.