willc0de4food

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!

Showing Posts 1 to 6

msmithstubbs

msmithstubbs

Before Phoenix 1.7 error_tag was a function defined for you in the ErrorHelpers module (source).

Since 1.7 there is a CoreComponents module. If has an <.input /> component that renders an input field with error feedback using <.error />. So you could use that:

<.input field={@form[:some_field]} type="hidden" />

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].errors and render it as you like.

The Phoenix Form Bindings guide discusses using phx-feedback attribute for styling and hiding error messages.

Updated: Just noticed LiveView 1.0 will drop support for phx-feedback.

willc0de4food

willc0de4food OP

Oh, that’s awesome. That actually works great, idk why I didn’t think of that :sweat_smile:
Thanks!

willc0de4food

willc0de4food OP

After implementing this, it does work but I’m also getting warnings in the console about it. Do you just ignore them? Lol

     warning: attribute "type" in component NuzzleWeb.CoreComponents.input/1 must be one of ["checkbox", "color", "date", "datetime-local", "email", "file", "month", "number", "password", "range", "search", "select", "tel", "text", "textarea", "time", "url", "week"], got: "hidden"
     │
 142 │             <.input type="hidden" field={@form[:gender]} />
     │             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     │
     └─ lib/nuzzle_web/live/quote.ex:142: (file)
LostKobrakai

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

willc0de4food OP

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

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:

<.error :for={msg <- Enum.map(@form[:gender].errors, &translate_error(&1)}><%= msg %></.error>
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
kszambelanczyk
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
RemyXRenard
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
velrest
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
samoloth
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
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews