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?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync. Next: ElixirConf EU 2027
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Qqwy
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:
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
<input type="checkbox" checked={@boolean}>should just work.jaimeiniesta
Makes sense, I would prefer to be able to generate valueless attributes like
checkedinstead ofchecked=truebut it’s not that important, just checking if there was a way to do that.Thanks!
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
Ah! It does! The following works as expected, generating a valueless attribute for
trueor no attribute forfalse.Awesome, thanks!
crockwave
Here is a
Surfacereference onboolean attributes. Is there corresponding documentation in Phoenix Liveview on this subject that we can reference?Surface (surface-ui.org)