knoebber
Components without LiveView - I thought this component syntax could only be used within a liveview
Hello,
I was looking over the code generated by phx.gen.auth in my app and I noticed this:
<.form
let={f}
for={@password_changeset}
action={Routes.user_settings_path(@conn, :update)}
id="update_password"
>
Source in phoenix: https://github.com/phoenixframework/phoenix/blob/master/priv/templates/phx.gen.auth/settings_edit.html.heex#L5
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 v4.3.0
Anyone care to explain? Thanks!
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked
Eiji
Possibly related:
https://github.com/phoenixframework/phoenix_html/issues/372
knoebber
Ok, I found it explained here:
https://hexdocs.pm/phoenix/views.html#html-components
Should the
Phoenix.HTMLdocs be updated to include examples with HTML components?Eiji
The link is not dead, because it’s just invalid. For all
hexpackages if there is no version inurlthenhexassumes 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
archive.orgshowsphoenixversion1.6.15, so let’s add it tourland “magically” it would work without any problem:https://hexdocs.pm/phoenix/1.6.15/views.html#html-components
Ok, so what’s happen? Let’s take a look for a last commit doing something about
guides/views.mdfile:[phoenixframework/phoenix cd049a33] Update guides.
As we can see the file has been renamed to
components.md, so here is up-to-date link:https://hexdocs.pm/phoenix/components.html
and if you want to have a link to a specific version let’s take latest:
https://hexdocs.pm/phoenix/1.7.7/components.html
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: https://hexdocs.pm/phoenix/Mix.Tasks.Phx.New.html#module-options