wwaldner
I would like to setup a nested form using a map. The form_for and to_form accept a map and this works for a single level form.
%{"name" => "fred"} |> Phoenix.Component.to_form() # this works and allows editing the name field using html form.
but would I expect the following to work?
%{"name" => "fred", "addresses" => [
%{"street" => "12342 S. Park" },
%{"street" => "1 N. Dump Rd" },
]} |> Phoenix.Component.to_form() # ???
I am trying to build up a map that has parent with multiple children. User would have a “add more” button to add another address. I have this working using changeset and associations, but have not seen case where this works with maps.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 7 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
codeanpeace
Yup, good catch!
To re-clarify,
to_form/1accepts either Ecto changesets or maps and converts them into aPhoenix.HTML.Formstruct.And
inputs_for/1requires aPhoenix.HTML.FormFieldstruct for itsfieldattribute which you can access through an aforementionedPhoenix.HTML.Formstruct.LostKobrakai
That‘s not true. It doesn‘t care for ecto. It requires a working
Phoenix.HTML.FormDataprotocol implementation just like all other phoenix form APIs. The implementation for ecto certainly includes a lot of bells and whistles and I wouldn‘t call the map based implementation to be „feature complete“, but inputs_for can work with map based forms for simple cases.codeanpeace
Ahh, yeah –
inputs_for/1expects an Ecto schema with either associations or embeds defined.wwaldner
I don’t have a Ecto schema for this, so not sure if embeds apply. I am trying to use the input_for and so far have not been able to get very far. Latest error I get is:
codeanpeace
Have you tried setting up addresses as embeds together with Phoenix.Component.inputs_for/1 within the form in the template?
wwaldner
I would not be too concerned about errors..yet. Would love to get the basics working. Any I could look at for an example of something like this?
LostKobrakai
This is only partially supported by the map based implementation. Most importantly there‘s no way to handle errors for nested inputs.