fix: use correct syntax for boolean attributes #317
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Another issue I noticed by running html-minifier (I am adding an
itemscope
).Interestingly, it seems the typeof undefined check will never be true
(at least with ssr). I wasnt able to give my attribute an undefined value to only print the attribute tag (edit: not sure where but in my Nuxt project somewhere betweennuxt:getNuxtConfig
andvue-meta:getMetaInfo
the attributes with undefined values are completely stripped).There are quite a bit of attributes which should never be used on a html/body, but for the sake of completeness I still included them. Maybe in a next major version we could just do a type check on
data[attr] === true
, but that again could result in invalid html when passing custom attributes so not sure what would be best