DIO 8

[thysultan]

Ready for the most part, mostly tweaking the level of abstractions to allow for a clean transition into the 2-phase commit->flush approach for the next minor release before/when react fiber(async mode) is released and cooperative scheduling is proven a necessary abstraction.

Currently the infrastructure looks like reconcile -> commit -> renderer.
The transition would make it look like reconcile -> commit ... [DOM/Native...]renderer(commits).

[coveralls]

Changes Unknown when pulling 8ae3e87 on V8 into ** on master**.

[thysultan]

Agreed. I think we are finally close to a release. Did you find any other hiccups?

[coveralls]

Changes Unknown when pulling 99f3672 on V8 into ** on master**.

[Zolmeister]

I'm working on a safari mobile diffing issue, but I say go ahead and cut a release-candidate.

Some high-level API notes:
I'd remove unmountComponentAtNode, seeing as it's equivalent to render(null, $el)
I'm weary of findDOMNode; it smells like a foot-gun (I don't see a good reason to use it over lifecycle methods, and even then direct DOM manipulation is generally a bad idea)

[coveralls]

Changes Unknown when pulling 05abc71 on V8 into ** on master**.

[thysultan]

unmountComponentAtNode and findDOMNode are mostly there for explicit React API parity.

I'm working on a safari mobile diffing issue

Hydration related?

[coveralls]

Changes Unknown when pulling 28e17c4 on V8 into ** on master**.

[coveralls]

Changes Unknown when pulling d845bcf on V8 into ** on master**.

[coveralls]

Changes Unknown when pulling b076cab on V8 into ** on master**.

[coveralls]

Changes Unknown when pulling 1ec562e on V8 into ** on master**.

[Zolmeister]

8.0.0-beta.0 deployed at https://gwent.io and https://deckswap.com
So far so good

[coveralls]

Changes Unknown when pulling bbcba6a on V8 into ** on master**.

[thysultan]

Are they both server rendered?

[Zolmeister]

The last commit did not include new/updated tests?

And yes, though note I'm using dio.js as the backend for Zorium (dio branch) which uses a component instance model that guarantees state persistence across DOM tree manipulation (fundamentally different from React)

For server-side rendering I crawl the vtree to fill state before stringification, and bail if too slow. (untilStable())

[thysultan]

The last commit did not include new/updated tests?

No, nothing changed that would requires new/updated tests.

I think the last point to settle on before release is whether to include the renderer package in the next minor release or with the 8.0 release.

[Zolmeister]

Because it opens up such a large public API, it might be best to let 8.0 settle a bit before introducing it

[coveralls]

Changes Unknown when pulling d3bbe6c on V8 into ** on master**.

[thysultan]

I agree, lets settle with that.