hogne
Hi
I’m using traverse_errors as described here: Ecto.Changeset — Ecto v3.14.0 to gather validation errors from a schema with an embed_many.
I get the following output (truncated for readability):
%{
mods: [
%{},
%{value: ["is invalid"]},
%{},
%{},
%{value: ["is invalid"]},
%{value: ["is invalid"]},
%{value: [...]},
%{...},
...
]
}
I would like to include the actual values that trigger the invalid failures, but can’t see any obvious way of doing it. Neither the Changeset.changes nor Changeset.errors seem to contain this information?
Any tips would be appreciated, thanks
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #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!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
wojtekmach
changeset.paramscontains values that are being casted, I think you’d have to manually traverse changesets (like traverse_errors does it) to match up values with errors.al2o3cr
Sounds like you might get what you’re looking for with the behavior
traverse_errorshas when you pass a function with arity 3, referenced briefly in the documentation:Combining the first two args using
Ecto.Changeset.get_change(changeset, field)will get you the value that triggered the validation error.hogne
Hi
Thanks for the replies.
I have been testing with passing a function with arity 3 now and that gives me access to the entire changeset. get_change was convenient, but it seems if the error is a cast error then Changeset.changes doesn’t include the key:value pair that failed at all. If the error was an inclusion error it is included.