Skip to content

Gold

Choose a tag to compare

@hershel-theodore-layton hershel-theodore-layton released this 30 Jul 16:19
· 24 commits to master since this release

This release changes the Flow game by increasing the amount of flows threefold.

For the upgrading guide, see upgrading-from-v0-to-v1. There are a couple of breaking changes, but almost all code written before today is compatible with v1.0.x. Upgrading should be a breeze.

In short, this release adds two brand new flow kinds:

  • Successor<Flow>
  • Init<Flow>

The original / classic flow has been dubbed Descendant<Flow>. All three can still be passed to method expecting a Flow. They share the same familiar Flow methods, but they solve problems that previously required workarounds or global / static variables.

The Init<Flow> is meant to solve the following issue, how do I make decisions based on Flow in a DissolvableElement? The Init<Flow> is available everywhere.

The Successor<Flow> is meant to create order in an asynchronous world. Writes happen in source order. Reads are guaranteed to observe all writes from ancestors and none of the successors. Adding event handlers or otherwise dynamic <script> tags was the motivating use case.

A couple of components have been superseded. Those components have a @deprecated tag in their doc comments. You are still able to use them, but use of the new components is encouraged. There are no plans to remove the deprecated components in the near future.