iacobson

iacobson

Hi,

What would be a good way to pass some information from the conn to the LiveView socket ?
Let’s assume the following example

router.ex

scope "/admin", MyAppWeb.Admin do
  ......
  pipe_through :ensure_admin_authenticated
  live "/article/:id/edit"
end

In my ensure_admin_authenticated plug I check the current user, see if it is admin and assign it to the conn.

I would like to have that available in the LiveView socket. For example, if I render the LiveView from a controller, I can use the session to pass the user, but I would not want to use controllers if possible.

Thanks

Showing Posts 1 to 5

chrismccord

chrismccord

Creator of Phoenix

You can a combination of assign_new and the session. Assuming your :ensure_admin_authenticated plug places a user_id key in the session, you can tell the live macro in the router to copy the conn session key to the LV session. Then on mount, you can use assign_new to first check the parent assigns for the :current_user, and fallback to lookup from the session. This allows the initial HTTP render to only fetch the user once via your plug. Then when the LV mounts in a connected state from the client, it will fallback to lookup the current_user from the session. For example:

scope "/admin", MyAppWeb.Admin do
  ......
  pipe_through :ensure_admin_authenticated
  live "/article/:id/edit", session: [:user_id]
end

...

def MyLive do

  def mount(%{user_id: user_id}, socket) do
    {:ok, assign_new(socket, :current_user, fn -> lookup_user(user_id) end)}
  end
end
17
Post #1
iacobson

iacobson OP

Thanks Chris !

setting the user_id in the session worked perfectly.

For anybody following this subject, I ended up with a route like
live "/article/:article_id/edit", EditArticleLive, session: [:path_params, :current_user_id]

However, the assign_new only half worked for my case. In your example above it would always lookup_user/1 for me when the LV mounts.

If I inspect the conn, the first iteration would be

%Phoenix.LiveView.Socket{
  assigns: %{
    current_user: %MyApp.Accounts.Schema.User{
      __meta__: #Ecto.Schema.Metadata<:loaded, "users">,
      id: 3,
      ...
    },
    my_text: ""
  },
  changed: %{current_user: true, my_text: true},
  connected?: false,
  endpoint: MyAppWeb.Endpoint,
  fingerprints: {nil, %{}},
  id: "phx-+acWjg8b",
  parent_pid: nil,
  private: %{
    assigned_new: {%{
       current_user: %MyApp.Accounts.Schema.User{
         __meta__: #Ecto.Schema.Metadata<:loaded, "users">,
         id: 3,
         ...
       }
     }, [:current_user]}
  },
  stopped: nil
}

Which looks fine to me.
But then in the second iterations turns into this, if I do not fetch the User

%Phoenix.LiveView.Socket{
  assigns: %{current_user: nil, my_text: ""},
  changed: %{current_user: true, my_text: true},
  connected?: true,
  endpoint: MyAppWeb.Endpoint,
  fingerprints: {nil, %{}},
  id: "phx-noktpWPS",
  parent_pid: nil,
  private: %{assigned_new: {%{}, [:current_user]}},
  stopped: nil
}
jihantoro

jihantoro

hi @chrismccord , sorry non-LiveView question, how do i pass , session: [:user_id] to all routes inside specify scope

askasp

askasp

Hi! This does not seem possible anymore after this commit Remove deprecate features · phoenixframework/phoenix_live_view@0020c35 · GitHub Is there a alternative way of achieving the same?

mekusigjinn

mekusigjinn

ooh something I might be of help!

# at router.ex:
...
live "/", ThisIsLive #no need to do "session: ..."
...
put_session(conn, :session_id, session_id)

# at LiveView:
...
def mount(_params, session, socket) do
    session_id = session["session_id"]
   # session has whatever you pushed in router, via put_session()
...
end
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
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
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews