fix: loading interfaces for derived loaders

[saihaj]

we don't support interfaces as loaders in graph-node so we should not be generating any derived loader for interfaces

closes #1449

[changeset-bot]

🦋 Changeset detected

Latest commit: f349bfd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@graphprotocol/graph-cli	Minor
lens-protocol-posts-sg	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	f349bfd
Status:	✅  Deploy successful!
Preview URL:	https://a0e77b1d.graph-tooling.pages.dev
Branch Preview URL:	https://saihaj-patch-interface-loade.graph-tooling.pages.dev

View logs

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphprotocol/graph-cli	0.59.0-alpha-20230928143131-f349bfd	npm ↗︎ unpkg ↗︎

[dimitrovmaksim]

Does this change mean you can't do parentEntity.childEntity.load() on entities where childEnitity points to an interface? More precisely that childEntity field won't exists on the parentEntity at all?

[saihaj]

@dimitrovmaksim correct asfaik in graph-node we don’t allow loading interfaces. When adding support for loaders we mistakenly created loaders for interfaces which could crash subgraph at runtime

[dimitrovmaksim]

@saihaj Then i suppose the docs should point out that Interfaces are not supported for derived fields, because it seems some devs use them.