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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
ICal is a library for interacting with iCalendar data. It parses iCalendars into typed Elixir structs via ICal.from_ics, and can prepare ...
New
Latest Phoenix Threads
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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: