willc0de4food
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 working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
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
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
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: