Why handle className?

[jorgebucaran]

This works:

const node = <div class="foo">ok</div>

This also works:

const node = html`<div class="foo">ok</div>`

Maybe I forgot, but I don't see what's the point of supporting className in HyperApp.

[jorgebucaran]

This seems to be related:

• add hyperscript-attribute-to-property choojs/hyperx#22

Unfortunately, this seems to be an issue with how Hyperx creates both classname and class attributes in elements, so we need to support className, otherwise HyperApp would fail to toggle a class name when using Hyperx.

[tunnckoCore]

it is not related to anything. just kinda convention because such are keywords in js. that is the case with "for" -> "htmlFor", and http-equiv to httpEquiv

[jorgebucaran]

Sure, I think I know that pretty well. The issue here is that Hyperx adds a classname property to elements and there is no way to turn it off which forces us to handle it specifically.

[ngryman]

Related: #85.