On nested-style boolean inputs, it's possible to opt-out of the hidden input
generation by passing the include_hidden: false option.
However, for inline inputs, this still generates the hidden field, causing
an inconsistency between the two boolean styles, and a whole lot of late night confusion.
A workaround has been proposed in a comment from 2016,
which consists in passing include_hidden in the input_html. I think this is
not ideal, as it causes inconsitencies between the APIs of the boolean styles.
This PR makes the inline checkboxes honor the include_hidden styles, making their API consistent.
On
nested
-style boolean inputs, it's possible to opt-out of the hidden input generation by passing theinclude_hidden: false
option.However, for
inline
inputs, this still generates the hidden field, causing an inconsistency between the two boolean styles, and a whole lot of late night confusion.A workaround has been proposed in a comment from 2016, which consists in passing
include_hidden
in theinput_html
. I think this is not ideal, as it causes inconsitencies between the APIs of the boolean styles.This PR makes the inline checkboxes honor the
include_hidden
styles, making their API consistent.