Let’s me start out with a new project based on generators:

Using mix phx.gen.live gives me form_component.ex, index.ex and show.ex for my schema. The latter two use the form_component.ex as a modal:

<.modal :if={@live_action in [:new, :edit]} id="project-modal" show on_cancel={JS.patch(~p"/projects")}>
  <.live_component
    module={DemoWeb.User.FormComponent}
    id={@user.id || :new}
    title={@page_title}
    action={@live_action}
    project={@user}
    patch={~p"/userss"}
  />
</.modal>

or

<.modal :if={@live_action == :edit} id="project-modal" show on_cancel={JS.patch(~p"/projects/#{@project}")}>
  <.live_component
    module={DemoWeb.ProjectLive.FormComponent}
    id={@project.id}
    title={@page_title}
    action={@live_action}
    project={@project}
    patch={~p"/projects/#{@project}"}
  />
</.modal>

Now I am having a look at mix phx.gen.auth and was wondering how I could restrict only the modal usage (both :new and :edit) to registered users.

Ideas so far:

• Create a standalone live view form.ex and replace form_component.ex. But then I can not use it inside a modal (?). This way I could set authorization in my router.ex.
• Add a check in the relevant apply_action/3 in index.ex and use the same pattern in show.ex?
• Add checks to both existing live views: .modal :if={@live_action in [:new, :edit] and @current_user} in the heex?
• Pass the :current_user to the live component and let the live component handle the check?

I would prefer to handle this in the router.ex, just because then all restriction related logic would be defined at one point.

Any other ideas?