Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions .changeset/shy-experts-wink.md

This file was deleted.

10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Changelog

## 6.0.2

### Patch Changes

- [#115](https://github.com/tivac/xstate-component-tree/pull/115) [`51cfe5e`](https://github.com/tivac/xstate-component-tree/commit/51cfe5e145106268a3fa94b4a30ed76a3f48cd30) Thanks [@tivac](https://github.com/tivac)! - Fix an issue where in specific situations child trees would not be built.

If a child machine has an `invoke` that immediately triggers a no-op event, the `ComponentTree` instance wouldn't actually walk that child machine for components to render. This was due to an interesting interaction between the xstate `.changed` property and when `invoke`s within the statechart are run.

Now whenever the `ComponentTree` sees a new machine it hasn't walked is running, it will walk it.

## 6.0.1

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "xstate-component-tree",
"version": "6.0.1",
"version": "6.0.2",
"description": "Build a tree of components based on statechart values",
"author": "Pat Cavit <npm@patcavit.com>",
"license": "MIT",
Expand Down