Closed ShMcK closed 5 years ago
This is by design, to closely match the behaviour of react-router (see https://reacttraining.com/react-router/web/api/Route). With children functions, there's an extra prop match
with the result of the condition.
See https://github.com/avaragado/xstateful-react#machine for the rules followed for the component
, render
and children
props.
Child functions appear to not listen to the is/not condition.