Notice the extra noise for the required attribute, which is needed so that a value of false omits the attribute entirely. (Per the HTML spec, any value for the required attribute means that the input is required, so the attribute must be omitted entirely.)
I can't think of a use case where the current behavior is convenient. My idea would technically be a breaking change, but (I think) worth it. Unless I'm missing a good use case for the current behavior.
Treat false attribute values like null/undefined
I noticed that when an attribute value is
null
orundefined
, it's omitted entirely:This is convenient (and maybe worth mentioning in the README as a feature) because I can have fewer conditionals in my code.
However,
false
is handled differently:In particular, this is a (very slight) pain point when handling the
required
attribute of inputs.Notice the extra noise for the
required
attribute, which is needed so that a value offalse
omits the attribute entirely. (Per the HTML spec, any value for therequired
attribute means that the input is required, so the attribute must be omitted entirely.)I can't think of a use case where the current behavior is convenient. My idea would technically be a breaking change, but (I think) worth it. Unless I'm missing a good use case for the current behavior.