carlgleisner
In LiveView 1.0 (1.0.0-rc.7), I am using inputs_for/1 to render forms for a nested Ash resource and it’s working great with validation of the fields in the nested resource as well as validation of the attribute with the array of the resources itself.
So, I am able to show the error below the inputs_for/1 component. However, I’m unable to immediately use used_input?/1 in order to delay showing this error until the field of the attribute for the nested resource should be considered used, after submission in this case I would like to think.
Notably, the params do not include any entry for _unused_addresses which would have caused used_input?/1 to work.
- Is there an “idiomatic” way to handle this?
- Am I holding it wrong?
The attribute in question
attribute :addresses, {:array, MyApp.MyDomain.PostalAddress},
allow_nil?: false,
public?: true
The field in the form
<.inputs_for :let={address_form} field={@form[:addresses]}>
Thank you in advance for any insights 
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash 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
- #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
- #blog-post
- #ai
- #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.
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
I believe this is fixed in
mainof Phoenix live view but not released yet.carlgleisner
Thanks Zach but I just checked on
mainand get the same result.Maybe you’re referring to this issue?
https://github.com/phoenixframework/phoenix_live_view/issues/2968
That fix from Chris fixed
used_input?/1for the fields on the nested resource itself though.carlgleisner
Retracting this last reply and investigating, sorry
carlgleisner
Hey I’d like to bump this post regarding using
inputs_foron a required attribute referring to an embedded schema and showing validation errors when left empty, but only when considered “used” in LiveView 1.0 terms.I’m running into this again and I, sincerely, cannot find any example or documentation to the effect.
While searching now I found this post on the forum (non Ash) where the poster @smon also attempted to show the errors manually within the
inputs_forbut faced the issue of the error message showing upon first validation, i.e. before it was “used” in the sense ofused_input?/1(that was not LiveView 1.0 I would guess).For now I’m just showing the error from the first validation but I’m getting questions about it.
zachdaniel
Since a lot of different things could be going on here, I think that the best thing to do here would be to make a reproduction.