caleb-bb
So, I want LiveView to keep track of a set of checkboxes and know which ones are checked and which are not. The purpose of this is to keep track of, and modify, a many_to_many association between billing_categories and credit_cards.
In my .html.heex I have:
<div>
<%= category %>:
<input checked={category in @changeset.data.billing_categories} type="checkbox" phx-click="flip" value={category}>
</div>
<% end %>
And then in my live controller:
def handle_event("flip", params, socket) do
IO.inspect(params, label: "Well looky here!")
{:noreply, socket}
end
When I check the box with the name "1", I get this in the terminal from inspecting the params:
Well looky here!: %{"value" => "whoa!"}
But when I uncheck a box, I just get:
Well looky here!: %{}
If I could just get handle_event/3 to know which box has been unchecked, I could take care of the rest. Is there some simpler way to do this?
Trending in Questions
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
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
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
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
st4ll1
You can use a with the same name as the checkbox and set its value to whatever you want.
this is what it looks like in the core_components.ex from phoenix_live_view
caleb-bb
Pardon me, but can use a what? Your sentence appears to be missing a word there!
LostKobrakai
The behaviour you see is how html is supposed to work. Unchecked checkboxes are ignored when gathering a forms data.
I‘d suggest using the form helpers of phoenix to build checkboxes. They automatically add an hidden input as well (before the checkbox), which uses the same name and has an „unchecked“ value. So when the checkbox is not checked you get the value of the hidden input – when the checkbox is checked you get the value of the checkbox, which overrides the hidden input value.
st4ll1
My bad, to mark it as code,
there was a
<input type="hidden" name={@name} value="false" />like in the example below