hoetmaaiers

hoetmaaiers

I want to redirect the Phoenix router to a specific page so “/” renders the first navigation item.

Currently I do this using a root page:

# router.ex
defmodule AppWeb.Router do
   ...
  scope "/", AppWeb do
    pipe_through :browser



    live_session :navigation, on_mount: [AppWeb.Navigation] do
      live "/", RootLive.Index
      live "/comics", ComicLive.Index
      live "/comics/new", ComicLive.New, :new
      live "/comics/:id", ComicLive.Show, :edit
      ...

In RootLive.index this happens:

defmodule StripeljeeWeb.RootLive.Index do
  use StripeljeeWeb, :live_view

  def handle_params(_unsigned_params, _uri, socket) do
    {:noreply, socket |> redirect(to: "/comics")}
  end

  def render(assigns) do
    ~H"""
    ...
    """
  end
end

This does work, but Dializer complains about this:

Type mismatch for @callback mount/3 in Phoenix.LiveView behaviour.

Expected type:

  {:ok,
   %Phoenix.LiveView.Socket{
     :assigns => Phoenix.LiveView.Socket.assigns_not_in_socket() | map(),
     :endpoint => atom(),
     :fingerprints => {nil | binary(), map()},
     :host_uri =>
       :not_mounted_at_router
       | %URI{
           :authority => URI.authority(),
           :fragment => nil | binary(),
           :host => nil | binary(),
           :path => nil | binary(),
           :port => nil | char(),
           :query => nil | binary(),
           :scheme => nil | binary(),
           :userinfo => nil | binary()
         },
     :id => binary(),
     :parent_pid => nil | pid(),
     :private => map(),
     :redirected => nil | tuple(),
     :root_pid => pid(),
     :router => atom(),
     :transport_pid => nil | pid(),
     :view => atom()
   }}
  | {:ok,
     %Phoenix.LiveView.Socket{
       :assigns => Phoenix.LiveView.Socket.assigns_not_in_socket() | map(),
       :endpoint => atom(),
       :fingerprints => {nil | binary(), map()},
       :host_uri =>
         :not_mounted_at_router
         | %URI{
             :authority => URI.authority(),
             :fragment => nil | binary(),
             :host => nil | binary(),
             :path => nil | binary(),
             :port => nil | char(),
             :query => nil | binary(),
             :scheme => nil | binary(),
             :userinfo => nil | binary()
           },
       :id => binary(),
       :parent_pid => nil | pid(),
       :private => map(),
       :redirected => nil | tuple(),
       :root_pid => pid(),
       :router => atom(),
       :transport_pid => nil | pid(),
       :view => atom()
     }, Keyword.t()}


Actual type:

  {:noreply,
   %Phoenix.LiveView.Socket{
     :redirected => {:redirect, map()} | {:live, :patch | :redirect, map()},
     _ => _
   }}

Showing Posts 1 to 8

D4no0

D4no0

The mount/3 callback should return data in format {:ok, socket} not how you would do when handling an event: {:noreply, socket}.

hoetmaaiers

hoetmaaiers OP

Sorry, but how does this relate? I try to understand but can’t.

When defining a mount callback like this:

  def mount(_params, _session, socket) do
    {:ok, socket}
  end

The warning from dialyzer is not much different:

Type mismatch for @callback mount/3 in Phoenix.LiveView behaviour.

Expected type:

  {:ok,
   %Phoenix.LiveView.Socket{
     :assigns => Phoenix.LiveView.Socket.assigns_not_in_socket() | map(),
     :endpoint => atom(),
     :fingerprints => {nil | binary(), map()},
     :host_uri =>
       :not_mounted_at_router
       | %URI{
           :authority => URI.authority(),
           :fragment => nil | binary(),
           :host => nil | binary(),
           :path => nil | binary(),
           :port => nil | char(),
           :query => nil | binary(),
           :scheme => nil | binary(),
           :userinfo => nil | binary()
         },
     :id => binary(),
     :parent_pid => nil | pid(),
     :private => map(),
     :redirected => nil | tuple(),
     :root_pid => pid(),
     :router => atom(),
     :transport_pid => nil | pid(),
     :view => atom()
   }}
  | {:ok,
     %Phoenix.LiveView.Socket{
       :assigns => Phoenix.LiveView.Socket.assigns_not_in_socket() | map(),
       :endpoint => atom(),
       :fingerprints => {nil | binary(), map()},
       :host_uri =>
         :not_mounted_at_router
         | %URI{
             :authority => URI.authority(),
             :fragment => nil | binary(),
             :host => nil | binary(),
             :path => nil | binary(),
             :port => nil | char(),
             :query => nil | binary(),
             :scheme => nil | binary(),
             :userinfo => nil | binary()
           },
       :id => binary(),
       :parent_pid => nil | pid(),
       :private => map(),
       :redirected => nil | tuple(),
       :root_pid => pid(),
       :router => atom(),
       :transport_pid => nil | pid(),
       :view => atom()
     }, Keyword.t()}


Actual type:

  {:noreply,
   %Phoenix.LiveView.Socket{
     :redirected => {:redirect, map()} | {:live, :patch | :redirect, map()},
     _ => _
   }}


D4no0

D4no0

If you have changed the code and the warning still persists, try to delete the _build folder and start the server again, sometimes there are cache bugs.

sodapopcan

sodapopcan

This line looks wrong. Unless there is a default identifier you can use that I don’t about, it should either look like: on_mount: [{AppWeb.Navigation, :some_identifier}] or just on_mount: {AppWeb.Navigation, :some_identifier} if you only have one callback.

hoetmaaiers

hoetmaaiers OP

@D4no0 this makes no difference. Restarting the Elixir language server also solves nothing. Running mix phx.server does not show this error, only ElixirLS shows the warning.

If you have changed the code and the warning still persists, try to delete the _build folder and start the server again, sometimes there are cache bugs.

@sodapopcan I looked into this through the documentation and I indeed use the :default identifier.

LostKobrakai

LostKobrakai

The error still lists the actual type as {:noreply, …}, where {:ok, …} is expected. So that’s what you should be looking out for.

D4no0

D4no0

You should have started with the fact that the problem comes from ElixirLS, the build folder for elixir-ls for vscode is located in .elixir_ls. What I do in such cases is close code editor, remove _build, .elixir_ls and then it should compile everything from a clear start.

I’ve been also noticing having a lot of times this happen lately, maybe a bug introduced in some update, hopefully it will be fixed soon.

hoetmaaiers

hoetmaaiers OP

Thank you for pointing out that elixir_ls has its own .elixir_ls folder. Deleting this solved its complaints.

— All posts loaded —

Where Next? Top

Trending in Questions Top

Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
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
psy-q
I’m trying to set up Emacs with elixir-ls via lsp-mode and credo via Flycheck. This should mostly be preconfigured as Flycheck picks up c...
New

Other Trending Topics Top

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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews