You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check if updating to the latest Preact version resolves the issue
Describe the bug
When I include a boolean attribute in a web component I expect it to be considered true, much like react does. For example, <my-web-component truthy-attribute ></my-web-component> , but instead I must always include a value truthy-attribute=true .
Note: I was looking into diff/props and I thought to open a pull request to handle undefined alongside null but had no way of trying it locally so not sure if it would have worked
The text was updated successfully, but these errors were encountered:
This issue seemingly lacks a bit of context 😅 we ask for a reproduction for a reason, either provide us with a failing test in our test-suite (which is also a way to test your changes btw) or a stackblitz reproduction. When I write a test in our test-suite that renders <my-component the-truth /> I correctly see this translated to <my-component the-truth='true' /> in the DOM. Not sure what different behavior your are expecting here as the issue isn't describing that.
To make this actionable we'll need to get a reproduction with the actual/expected behavior defined, then we can have a conversation about expectations.
Describe the bug
When I include a boolean attribute in a web component I expect it to be considered true, much like react does. For example,
<my-web-component truthy-attribute ></my-web-component>
, but instead I must always include a valuetruthy-attribute=true
.Note: I was looking into
diff/props
and I thought to open a pull request to handle undefined alongside null but had no way of trying it locally so not sure if it would have workedThe text was updated successfully, but these errors were encountered: