Why LiveComponent mount/1 socket doesn't keep the assigns from liveview parent?

You can get the current user using the session instead.

 @impl true
  def mount(_params, %{"user_id" => user_id}, socket) do
    {:ok, assign_new(socket, :current_user, fn -> Accounts.get_user!(user_id) end)}
  end

About assigns from the parent components, I think it is better to pass it directly(like React and or Vue.js does)

live_component(socket, MyAppWeb.ModalComponent, :assign1: "bla", assign2: @assign2 )

So that way you can pass only what is needed to the child component, keeping it lightweight.

But, no sure if we should do that db call on every child component. Perhaps, it is better to pass user details as assings to child components.

Yep, the problem in the component is the only place where you have that id is in update or preload functions, so you need to add extra logic to only perform queries once.

If we had the assigns available in mount we didn’t have to take care doing extra request on updates.

Did you evaluate if you can have a child template instead of another component?

<%= render "child_template.html", assigns %>

Great question.
Initializing anything useful can only be done in update/2.
mount/1 needs (readonly) access to “parent” assigns to become useful.
I have spent many hours finding a solution without any success.
Please update when you find something.

I am also in that same state. Needing to retrieve useful information from the main liveview to my live_component that has mount / 1

you are aware that you can copy the state from parent to child (using assign) ?
(and have as many copies of the parent assigns as you have children LiveComponents)
what you can’t do is read the parent state once while mounting and translate (some of) the parent state into an independent child state.
(we would want that of course)

Yes, but i thought about the same possible scenario that you covered, about mount and convert the parent state into an independent child state. That concept would be interesting

I just proposed a (maybe) possible solution here:

Let’s see what happens.

So @josevalim has some serious concerns about potential issues when using contextual data that is not change tracked within the LiveComponent.