Skip to content

Conversation

@TylerBarnes
Copy link
Contributor

@TylerBarnes TylerBarnes commented Jun 14, 2023

Description

Looks like in #37782 type owners check was added to the TOUCH_NODE action which is likely causing this issue. I tried this PR locally on a repro from the linked issue and it seemed to resolve it.

canary available as [email protected]

Related issues

Fixes #38117

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Jun 14, 2023
@TylerBarnes TylerBarnes requested review from LekoArts and pieh June 14, 2023 22:48
@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 Jun 15, 2023
@LekoArts LekoArts changed the title fix: allow touching nodes owned by another plugin fix(gatsby): allow touching nodes owned by another plugin Jun 15, 2023
Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like it actually restore previous behavior. Previously touchNode would only set local variable typeOwners based on touched node's .internal.owner but would not actually try to validate it. Now type ownership is just preserved between builds so not checking it here restores previous behavior as much as possible.

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.

The plugin "gatsby-source-name" created a node of a type "File" owned by "gatsby-source-filesystem"

4 participants