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 aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Other Trending Topics
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
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
- #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
- #performance










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: