nicky

nicky

The application I’m developing has a background gradient that I noticed flashing between liveviews so I inspected the dom and was surprised to see the layout re-rendered w/ each transition to a new liveview. I’m specifying the :layout and I’ve got a live_session wrapping the liveviews in the router and I’m using push_navigate to navigate between liveview. In the documentation it says live sessions keep the same layout, which it is, but I thought that would mean the layout elements was tracked and not re-rendered without changes to their props. Or am I doing something wrong?

Liveview:

  @impl true
  def handle_event("continue", _, socket) do
    {:noreply, push_navigate(socket, to: ~p"/provider/enter-mrn")}
  end

Router:

  scope "/provider", ProviderWeb do
    pipe_through([:browser])

    live_session :provider,
      layout: {ProviderWeb.Layouts, :provider},
      on_mount: [{ProviderWeb.ProviderHooks, :version}] do
      live("/welcome", WelcomeLive, :index)
      live("/enter-mrn", MRNLive, :index)
      live("/enter-dob", DOBLive, :index)
      live("/orders", OrdersLive, :index)
    end
  end

layout:

<link phx-track-static rel="stylesheet" href={~p"/assets/provider"} />

<ProviderWeb.CoreComponents.header />

<main class="provider">
  <%= @inner_content %>
</main>

<footer class="provider">
  <p>
    version: <%= @version %>
  </p>
</footer>

Showing Posts 1 to 4

sodapopcan

sodapopcan

Hello and welcome!

Is says the root layout (:root_layout vs :layout) is not updated between redirects (if they share one), everything else is. This is the static layout generally shared between live views and dead views alike and is not change tracked—it’s generally rendered once can have its title updated through the special assign :live_title.

nicky

nicky OP

I was hoping I did something wrong :frowning_face:

I appreciate your reply.

codeanpeace

codeanpeace

Have you tried creating a separate root layout specific to that live session? You should be able to do something like this:

live_session :provider,
      root_layout: {ProviderWeb.Layouts, :provider_root},

If you wanted to keep a single root layout, you could move the shared unchanging parts of the :layout into the :root_layout and put it behind a check based on the live_session by checking an assign set on mount or on_mount for the name of the live_session, which should be available somewhere in the session callback parameter.

nicky

nicky OP

thanks for the suggestion! the css attached to the layout was causing the issue so I created a plug that holds a list of css & js files that I loop through in the root layout. I’ll take your suggestion though and move the other common parts in the root layout behind a check.

— All posts loaded —

Where Next? Top

Trending in Questions Top

water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New

Other Trending Topics Top

budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews