Gatsby references

[Leksat]

Package(s) involved

amazeelabs/silverback_gatsby

Description of changes

Whenever we track an update on an entity, get all its usages and track the source entities as well.

Motivation and context

gatsby-graphql-toolkit creates node references in Gatsby data layer. Yet it does not clean them up when a target node is removed.

    if (node) {
      context.gatsbyApi.actions.deleteNode(node)
    }
    // TODO: find all nodes referencing deleted nodes and update/refetch all of them?

https://github.com/gatsbyjs/gatsby-graphql-toolkit/blob/cec93fe2457aa0de64dbdeb759626010d9fe270a/src/source-nodes/node-actions/delete-nodes.ts#L17-L20

Related Issue(s)

#1274

How has this been tested?

Manually. Added an integration test case.

[Leksat]

It should have fallen on the test commit, yet it did not. I don't know why.

Locally it fails properly. But in CI an incremental Gatsby build sources all nodes for some reason.

Another evidence that we need to get rid of @amazeelabs/silverback-playwright ASAP. Will do in a separate PR.

[pmelab]

So its not going to recursively update chains, right? Just the direct parent level. Should be good enough for the Gutenberg use case.

[Leksat]

Yes, just direct parents.

Still I'm a little concerned about the performance. What if we get an entity used in 1k other entities 🙈 Time will tell 😅