a) they use the same method names like the `kotlin-html` package ("div{}" et. al.), only they create ReactElement instead of manipulating the dom. This could be confusing.
b) The type-safe scoping mechanism, so that each scope has it's correct prop-setters and won't inherit setters from a scope further up is rather complex. It uses extension methods with multiple receivers plus operator overrides for `invoke()`.
That is rather complicated to follow so I want to try it out for some time to check if there's confusion or subtle bugs.
c) I haven't optimised for (allocation-)performance yet.
d) I'm using an early-access version of kotlin 1.1.4 which isn't out yet.
I have not published them, because
a) they use the same method names like the `kotlin-html` package ("div{}" et. al.), only they create ReactElement instead of manipulating the dom. This could be confusing.
b) The type-safe scoping mechanism, so that each scope has it's correct prop-setters and won't inherit setters from a scope further up is rather complex. It uses extension methods with multiple receivers plus operator overrides for `invoke()`.
That is rather complicated to follow so I want to try it out for some time to check if there's confusion or subtle bugs.
c) I haven't optimised for (allocation-)performance yet.
d) I'm using an early-access version of kotlin 1.1.4 which isn't out yet.