Components as classes and/or traits (ES6?)

React is moving towards ES6 classes being the default form of existence for components. Voices in gitter all approve a similar transition in Scala.

Note: This will be in addition to ReactComponentB which won’t be removed.

[japgolly]

Backends are getting closer and closer to components as classes. (63aea4a241f23f9a142e53926a4f5f49d176c7a3, #78)

Idea: with a small change we could do:

class Backend($: BackendScope[Props, State]) { ... }

val Component = ReactComponentB[Backend] // With macro, P S B all known in one step
  .initialState(...)
  .build

Can also set the DOM node type too:

class Backend($: BackendScopeN[Props, State, html.Table]) {

Actually this is great. A type with no constraints at all (a class construtor param) can tell us all the static information about a component in one line with no repetition anywhere else. Can even have different ReactComponentB path depending on static info. This should makes it easy to solve #171 too.

[japgolly]

As of 1.0, Scala component builder now creates ES6 classes (by default) for your Scala components. There’s also a unit test confirming that one can directly extend the ES6 facade and use it like any other component in scalajs-react.