linusdm
What actually triggers a validation in LiveView while doing live validation (without changing the database)?
Hi!
What actually triggers a validation in LiveView while doing live validation (without changing the database)? I’m struggeling with understanding how ecto changesets work in this regard. During live validation (the kind of validation that is added when using mix phx.gen.live) no changes are made to the database. I’m curious how this actually works, without inserting or updating the database.
Is the last line (Map.put(:action, :validate)) responsible?
changeset =
socket.assigns.model
|> Models.change_model(model_params)
|> Map.put(:action, :validate)
(or what does it do if that’s not the case?)
I’m in a situation where I want to trigger validation again, after using Changeset.change/2 on an existing changeset (which contains changes that are relevant and should be kept). Right now I’m creating a new changeset and triggering all validations again, but I suspect I’m doing this wrong. Any insight into understanding how and when valid? and errors is updated, is appreciated. I guess it must be explained somewhere in the docs, but I can’t find it here: Ecto.Changeset — Ecto v3.14.0
Thanks in advance!
Marked As Solved
LostKobrakai
It happens whenever you call Ecto.Changeset.validate_*. Changesets do not “register validations” they validate right when you call the API. This also means there’s no “rerun validations”. That’s simply not how changesets work. So you actually want to create the changeset fresh whenever you have new changes.
With LV you sometimes get partial changes. In this case I suggest first trying to find a way to not receive partial changes (e.g. integrate with the html form) or pulling out changeset.params and merge that with you new data as the input for a new changeset.
Also Liked
LostKobrakai
Validations run before constraints, because constraints are not run by ecto at all, but by the database. Ecto just converts error responses of the db to internal errors for constraints.
The :action is mostly about communicating intend. E.g. phoenix form error helpers only show errors if :action has a value. So you don’t need to create an errorless changeset as the inital changeset backing a form.
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #websockets
- #elixirconf-us
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
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!"