Components without LiveView - I thought this component syntax could only be used within a liveview

I was looking over the code generated by phx.gen.auth in my app and I noticed this:

    action={Routes.user_settings_path(@conn, :update)}

Source in phoenix:

I am confused how this works - I thought this component syntax could only be used within a liveview. I was expecting to see <%= form_for ... %>

The doc page for HTML.Form implies this as well: Phoenix.HTML.Form — Phoenix.HTML v3.3.2

Anyone care to explain? Thanks!


Possibly related:

1 Like

Ok, I found it explained here:

Should the Phoenix.HTML docs be updated to include examples with HTML components?

1 Like

Apologies for the necrobump, but this is the newest thread in this topic, and found a relevant GitHub issue:

The link above is dead, so here’s the archived version, just in case.

The link is not dead, because it’s just invalid. For all hex packages if there is no version in url then hex assumes latest version. The documentation may change, especially the guides that does not guarantee any API consistency can change often. The guide may be rewritten, renamed or simply deleted as said thing is no longer needed or solved in other way.

The page on shows phoenix version 1.6.15, so let’s add it to url and “magically” it would work without any problem:

Ok, so what’s happen? Let’s take a look for a last commit doing something about guides/ file:
[phoenixframework/phoenix cd049a33] Update guides.
As we can see the file has been renamed to, so here is up-to-date link:
and if you want to have a link to a specific version let’s take latest:

The issue has been closed over 1.5 year ago. Unfortunately it’s also not strictly relevant. Simply author of issue was expecting something to happen and therefore send a bug report.

If you wanted to mention the generator flags it would be better to link to the task’s documentation, see:

1 Like