Boolean `false` converted to string "false"

[jorgebucaran]

This makes it difficult (or impossible?) for a virtual DOM engine to determine whether the user meant false or "false".

html`${true}` // yields true
html`${false}` // yields "false"

If this is indeed determined to be a bug, I'd be delighted to help with if you'd be so kind to offer some help by pointing out where should I start looking in the code.

Cheers! 👋

[slaskis]

There's a PR to fix this: #35

[jorgebucaran]

@slaskis Why hasn't it been merged? 🤔

[slaskis]

In part because of this which might make it a possible breaking change for some. So I just wanted it reviewed/accepted by someone first.

But then I don't use this library much anymore so I kind of forgot 🤷‍♂️

[jorgebucaran]

Thanks. I think we can all agree hyperx should be agnostic about vdom implementations. So, perhaps your PR could be merged and that str.replace issue taken upstream to virtual-dom?

[jorgebucaran]

@substack Do you think #35 can be merged?