jaimeiniesta

jaimeiniesta

What is the proper way to interpolate boolean attributes like checked in an input in the new HEEx engine?

For example, in LEEx if I wanted to include it based on some condition, I would do this:


<input type="checkbox" name="web_pages[]" value="<%= w.id %>" <%= if w.id in @selected, do: "checked" %> />

Which would generate HTML like this:


<input type="checkbox" name="web_pages[]" value="1" />

<input type="checkbox" name="web_pages[]" value="2" checked />

Now in HEEx I do this


<input type="checkbox" name="web_pages[]" value={w.id} checked={if w.id in @selected, do: "true", else: nil} />

Which also works, if a nil value is passed then the checked attribute won’t be passed at all, but if I pass true then it will generate this:


<input type="checkbox" name="web_pages[]" value="2" checked="true" />

Which is correct, but longer and a bit uglier. I would have expected that this would work:


<input type="checkbox" name="web_pages[]" value={w.id} {if w.id in @selected, do: "checked"} />

But it doesn’t, it fails with protocol Enumerable not implemented for nil of type Atom. It looks like interpolation must always be bound to an attribute name in the HTML tag, right?

Showing Posts 1 to 6

Qqwy

Qqwy

TypeCheck Core Team

It is OK to assign to multiple dynamic attributes at once, using the syntax of your last example.

However, the result is expected to be a keyword-list or a map. Currently you are returning a single string.

Instead, you can do, for instance:

<input type="checkbox" name="web_pages[]" value={w.id} {if w.id in @selected, do: %{checked: true}} />

However, in neither case will the result be a valueless attribute.
I don’t think this is a bad thing. Instead, not supporting this special case makes it easier for the HEEx parser to always generate correct HTML.

LostKobrakai

LostKobrakai

<input type="checkbox" checked={@boolean}> should just work.

jaimeiniesta

jaimeiniesta OP

Makes sense, I would prefer to be able to generate valueless attributes like checked instead of checked=true but it’s not that important, just checking if there was a way to do that.

Thanks!

LostKobrakai

LostKobrakai

I’ve no heex project at hand to check, but I’m quite confident it just generates a valueless attribute or no attribute.

jaimeiniesta

jaimeiniesta OP

Ah! It does! The following works as expected, generating a valueless attribute for true or no attribute for false.

<input type="checkbox" name="web_pages[]" value={w.id} checked={w.id in @selected} />

Awesome, thanks!

crockwave

crockwave

Here is a Surface reference on boolean attributes. Is there corresponding documentation in Phoenix Liveview on this subject that we can reference?

Surface (surface-ui.org)

— 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
nseaSeb
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
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
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

JesseHerrick
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
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
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
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
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

Latest on Elixir Forum

Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews