Watching fields requires multiple-values checkboxes to have a `[]` name suffix about unpoly HOT 6 OPEN

The last checked checkbox with a given name is the one that goes into params.

I didn't say this correctly. This will work for keys with an [] suffix, as @adam12 mentioned. Here is a fork of @davisums' CodePen that changes the [name] to "status[]": https://codepen.io/triskweline/pen/rNbwMLj

from unpoly.

Unpoly autosubmits the form when the form's params ("form data") changes.

The checkboxes have the same [name]. The last checked checkbox with a given name is the one that goes into params. Hence checking other boxes before "Won't do" does not change the form's params.

You can use different names, or radio buttons.

from unpoly.

Unpoly autosubmits the form when the form's params ("form data") changes.

The checkboxes have the same [name]. The last checked checkbox with a given name is the one that goes into params. Hence checking other boxes before "Won't do" does not change the form's params.

You can use different names, or radio buttons.

It's a multiple-choice checkbox. I think that's the way those are typically rendered into HTML by both rails and django forms but I'll see if I can solve it some other way. Thanks for the help!

from unpoly.

It's a multiple-choice checkbox.

The [name] of a multiple choice checkbox usually ends with a [] to signify to the browser and server that there are multiple values attached.

ex.
<input type="checkbox" name="status[]">

from unpoly.

The [] suffix is a convention shared by many, but not all web frameworks. There is no web standard for it AFAIK.

It would technically be possible to detect multi-selects without that suffix. However doing this would somewhat complicate the callback signature of up.watch() and [up-watch]. In particular the oldValue and newValue arguments would always need to be arrays, for the rare case that we're dealing with a multi-select field.

from unpoly.

I had wanted to test if it would work with brackets. Thanks for pointing that out.

My first solution was to use Alpine for autosubmit (since it's already a dependency on this project) but I ended going with this instead on Django:

    post = request.POST.copy()
    post.setlist("status", request.POST.getlist("status[]"))
    form = FilterForm(post)

Since I don't want to use the form object to generate the HTML, this works fine in this case.

from unpoly.