Skip to content

Conversation

@Andarist
Copy link
Contributor

I think that this should resolve the issue reported by @pieh here: #36342 (comment)

Note that I have no knowledge about this code, I've just analyzed the shape of the machine, and how it's using this context data and I've concluded that it was mostly used locally by this particular invoke. It was, sort of, used as an argument for this service, and to achieve that it was first set on the context and later on removed from it (from within onDone). So since this was "temporary" context data, I've just refactored this to use what was already available on the event itself and removed the redundant code.

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Aug 16, 2022
@LekoArts LekoArts added topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Aug 17, 2022
@LekoArts LekoArts merged commit 9460dd3 into gatsbyjs:fix-xstate-option Nov 16, 2022
LekoArts added a commit that referenced this pull request Nov 16, 2022
pieh pushed a commit that referenced this pull request Nov 17, 2022
…#36342)

* update version and fix types

* yolo add option

* Work around removal of meta.state

* Refactor `meta.state` access in `gatsby-source-filesystem` (#36355)

Co-authored-by: Lennart <[email protected]>

* fix ts-ignore

* Upgrade XState to the latest 4.33.3 (#36451)

* update to latest xstate

* Use `pendingQueryRuns` available on the event (#36393)

* Revert "Use `pendingQueryRuns` available on the event (#36393)"

This reverts commit 9460dd3.

Co-authored-by: tyhopp <[email protected]>
Co-authored-by: Mateusz Burzyński <[email protected]>
Co-authored-by: Ty Hopp <[email protected]>
mwfrost pushed a commit to mwfrost/gatsby that referenced this pull request Apr 20, 2023
…gatsbyjs#36342)

* update version and fix types

* yolo add option

* Work around removal of meta.state

* Refactor `meta.state` access in `gatsby-source-filesystem` (gatsbyjs#36355)

Co-authored-by: Lennart <[email protected]>

* fix ts-ignore

* Upgrade XState to the latest 4.33.3 (gatsbyjs#36451)

* update to latest xstate

* Use `pendingQueryRuns` available on the event (gatsbyjs#36393)

* Revert "Use `pendingQueryRuns` available on the event (gatsbyjs#36393)"

This reverts commit 9460dd3.

Co-authored-by: tyhopp <[email protected]>
Co-authored-by: Mateusz Burzyński <[email protected]>
Co-authored-by: Ty Hopp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants