arcanemachine
How to add a global error to an Ecto changeset? (Not specific to a single field)
In Django, there is the concept of “non_field_errors”, which exists when a form field has an error that is not specific to any model field.
I am just wondering if there is a similar convention in Ecto. I have an error that is not specific to a single field. How should I describe it? Should I just use the django naming convention for the field, e.g. :non_field_errors? For example:
Ecto.Changeset.add_error(changeset, :non_field_errors, "some reason")
Just checking for recommendations. Thanks
Marked As Solved
sodapopcan
You can add those to :base.
Also Liked
arcanemachine
Interesting, that’s also what ChatGPT suggested. Is there any precedent for this specific value?
EDIT: The venerable Dogbert suggested the value :base in a Stack Overflow answer
sodapopcan
I’m assuming the precedent is Rails! It also uses :base.
arcanemachine
Cool, works for me. I just want to have some sort of convention to work with. The fewer decisions I have to make, the better.
Thanks Brother sodapopcan!
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
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.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"