Skip to content

Conversation

@github-actions
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

xstate-component-tree@8.0.0

Major Changes

  • #230 fdba194 Thanks @tivac! - Matching state and invoke names would cause xstate-component-tree to fail to return child components in some cases because internally it named them the same thing and stomped all over itself.

    states : {
        foo : {
            invoke : {
                id : "foo",
                // ...
            },
        },
    },
    

    This should work now.

    BREAKING CHANGE: All machine values in the output that previously looked like root.foo will now look like root.#foo, in order to help differentiate the child machine id from the parent state path.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 3999981 to eb0b560 Compare February 10, 2025 22:37
@github-actions github-actions bot force-pushed the changeset-release/main branch from eb0b560 to 671fa21 Compare February 10, 2025 23:59
@tivac tivac merged commit ee98f48 into main Feb 11, 2025
@tivac tivac deleted the changeset-release/main branch February 11, 2025 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants