Redo ALL the damn types

The types in this have become a giant mess. They’ve evolved as much as they can without a major rewrite. So it’s time for a major redesign of the types.

Problems

• Many types describe JS directly with ops added via implicits. Certain typically-simple functionality like mapping P, mapping S, CB vs direct, etc require so much annoying machinery (CompState) or just can’t be done (BackendScopeMP).
• Similarly, React rules are encoded in types by conjunction. A with B with C which makes general abstraction and mapping in pain when possible and impossible other times.
• Organisation is terrible as it’s either dump heaps in package.scala or add boilerplate everywhere like MonocleReact and ScalazReact. Yuk.
• [P, S, B, N <: TopNode] = pain in the ass.
• Too hard now to use types to prevent/allow .props.children.

Solution Ideas

• Just wrap all the bloody JS crap in Scala. One extra object instance per component (hopefully) isn’t going to make a noticeable dent in performance.
• Would be great to have a single class for components’ this and then have capabilities encoded as implicit permissions, phantom types, etc. The class could have all possible ops all the time (like in JS) but the permissions could be required to invoke them.
• Use existential types for backend and node type (and props children probably) with a few ∀ Aux helpers. Library provides in full. Gen code will mostly only specify [P, S].

[japgolly]

@ikamthania An update: I was hoping to get an RC out last week but 1) there were more changes still to make that I thought, and 2) being a new parent is significantly eating into my dev time 😦

An RC will be out sometime within the next 7 days.

[japgolly]

@ikamthania I can do you one better: progress is going well so I expect to publish RC1 later this week. 😃