move to new organization scalajs-react-interface about sri HOT 11 OPEN

from sri.

I like it alot. I've been converting my third party components over to that method independently, with 0.6.14 and 2.12 it's much nicer now, so I am huge +1 on that. For dom tags I actually copied @japgolly's approach and did https://github.com/dispalt/sri-vdom which I personally like; however, there are drawbacks as it doesn't give a ton of guarantees but suits my approach well.

Lack of macros will also speed up compile-time.

For 3rd party components, the 2nd con, you can use js.defined(f => foo) and it will handle the implicits, which again is nice.

from sri.

with 0.6.14 and 2.12 it's much nicer now

can you elaborate what 2.12 offers more for @ScalaJSDefined trait ..

For dom tags I actually copied @japgolly's approach and did https://github.com/dispalt/sri-vdom which I personally like; however, there are drawbacks as it doesn't give a ton of guarantees but suits my approach well.

👍 , actually my plan is to web module just contains ReactDOM facade and helpers and provide vdom in separate project https://github.com/chandu0101/sri-web-vdom ,so that users can come with different flavors of vdom which fits their taste buds/needs(server-rendering).Your use case is one classic example so lets do that.

For 3rd party components, the 2nd con, you can use js.defined(f => foo) and it will handle the implicits, which again is nice.

cool , thanks for the tip I'll update cons section :)

from sri.

from sri.

0.6.14 refers to SAM methods and leaving off type ascriptions.

we can hack around that by defining as vars! which will work fine 2.11/2.10.

from sri.

I don't see a good reason to combine renaming the artifacts with breaking changes. Even if you want to do them simultaneously the changes should have their own ticket. It will affect a lot of users and they might not find the discussion.

I object to at least some of them but it seems difficult to discuss on a ticket about something else.

from sri.

I object to at least some of them but it seems difficult to discuss on a ticket about something else.

fair enough , i'll create tickets for dom tags & third party & webstyles ,lets keep this for organization stuff.

from sri.

guys: what is your time frame for transition to https://github.com/scalajs-react-universe?

from sri.

once scala-js 0.6.15 released , I'll push first beta in couple of days.

Sjrd : Wait for 0.6.15
Andrea Peruffo @andreaTP Feb 26 19:26
sjrd ok, thanks!  any eta?
Sébastien Doeraene sjrd Feb 26 20:20
2-3 weeks, I would say

from sri.

great. probably would make sense to publish an S.R.U. "road map" on the org site?

from sri.

i created a ticket for this : https://github.com/scalajs-react-universe/support/issues/1 , lets use this until we release first beta,after that we'll discuss with community and create a detailed road map :)

from sri.