Bit of a bug in the way checkboxes handle "preventNonResponse"

[CarlosNZ]

The preventNonResponse flag is preventing the response from being saved at all when all checkboxes are empty. But there's no visual indication. So if you select, then unselect the checkboxes, then move on/submit, you'll actually be submitting a selected checkbox even if you intended to non select it. (You're not allowed to not select, but there should still be some visual indication)

I think the preventNonResponse flag is actually unncessary -- it can all be done with a validation expression.

The problem with the validation is, the "error" message shows up immediately, which is a bit ugly.

My suggestion would be to ditch the preventNonResponse option and replace it with an onlyValidateOnSubmit option which prevents any validation error appearing until submitting (or moving forward on in a linear application).

[CarlosNZ]

Actually, I can fix the immediate problem just by making it save a null response whenever the user unchecks all boxes and preventNonResponse is enabled. I've fixed that on develop so let's leave that as it is for now.

I have an idea of how to make it not show validation errors until submit/next is pressed, so I'll look into that briefly and make a PR here if it seems worth it.

[fergie-nz]

I'm still able to pass through validation without checking boxes with preventNonResponse = true, and isRequired = true

[CarlosNZ]

I'm still able to pass through validation without checking boxes with preventNonResponse = true, and isRequired = true

@fergie-nz I can't reproduce this on branch build_2023-03-11 or later, with my little fix I made in the weekend. Can you confirm you're using this?

[jagoje]

@CarlosNZ , @fergie-nz - is this one a non-issue now?

[CarlosNZ]

I'll need to check. It's not affecting the actual workflows we have in use, but I'll need to confirm how it's working for specific cases before closing this issue.