willc0de4food
Render error message for hidden field
Hello! I have a hidden input and I’m using buttons to set it’s value. The default value for this field is nil. If a user doesn’t select one of the options, I would like to show the error from the changeset beneath the buttons, like with other form fields that have automatic error handling. How can this be done?
I’ve seen references to an error_tag, but such a tag no longer exists as far as I can tell?
Thanks!
Trending in Questions
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Sta...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
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
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance











First 6 of 6 Posts
msmithstubbs
Before Phoenix 1.7
error_tagwas a function defined for you in theErrorHelpersmodule (source).Since 1.7 there is a
CoreComponentsmodule. If has an<.input />component that renders an input field with error feedback using<.error />. So you could use that:This will generate a hidden input field and the error feedback.
If you’d rather display the error yourself you can just access it directly:
@form[:some_field].errorsand render it as you like.The Phoenix Form Bindings guide discusses usingphx-feedbackattribute for styling and hiding error messages.Updated: Just noticed LiveView 1.0 will drop support for
phx-feedback.willc0de4food
Oh, that’s awesome. That actually works great, idk why I didn’t think of that
Thanks!
willc0de4food
After implementing this, it does work but I’m also getting warnings in the console about it. Do you just ignore them? Lol
LostKobrakai
<.input>bundles a bunch of markup around labels and errors together, which doesn’t really make sense for hidden inputs. You can just use a normal input and the<.error>component separately.willc0de4food
Are you aware of an example somewhere that shows what this would look like?
The only example I have come across with the
<.error>component is this, which doesn’t seem relevant for showing errors for a single input:<.error :for={msg <- @errors}><%= msg %></.error>LostKobrakai
Not sure how this wouldn’t seem relevant, but if you follow what happens as part of
<.input>it would show that it does the following eventually: