I feel like this should be documented somewhere
sushant12
i-n-g-m-a-r
thiagomajesk
Does anybody know if this is going anywhere? What have you been doing to solve this limitation?
I feel that perhaps the best solution would be passing the initial assigns as “params” to the live component mount callback. This way we won’t have to make any promises about making it “consistent” by keeping track of it. I think that this solves partially some of the concerns @josevalim had on the thread and addresses the point that those “params” are correct at that point in time.
Currently, it seems too difficult to decouple live components from the parent LiveView because of not being able to initialize itself with relevant data from outside (like querying something based on a param, for instance).
I don’t know about the API, but perhaps something like:
<!-- params or init special assign -->
<live_component module={Module} id={@id} params={foo: foo}/>
<live_component module={Module} id={@id} init={foo: foo}/>
<!-- or passing a tuple to initialize the module -->
<live_component module={{Module, foo: foo}} id={@id} />
1