Currently, the default implementation of shouldRejectValue only checks if the given value is an instance of Error.

Values of type Response with a status >=400 should be handled as errors by default too.

We need some basic test coverage for the core functionality.

Probably use prism.js

Support props.children of type function

The problem is that the entire handling is implicit and highly magic. It would be nice to have some more explicit mechanisms.

The doc states early / normal / late as possible values for the exit prop of the confirm component, while in code it must be started / finished / idle

When a <Stateful.Confirm> is placed inside a button, and the confirm has a "cancel" button that is clicked, this click event bubbles up and actually invokes the original button onClick - although the user explicitly canceled.

It would be great to have links to the previous and next examples on the bottom of each example page.