gatsby-source-contentful: Warn/error when content model uses Entry or Reference as content type

[axe312ger]

Oh right, I've misunderstood the question at first. Now I see that the problem is not with fields but with type names. The plugin defines interface types here:

gatsby/packages/gatsby-source-contentful/src/gatsby-node.js

Lines 327 to 340 in 3ffc210

	createTypes(`
	interface ContentfulEntry @nodeInterface {
	contentful_id: String!
	id: ID!
	node_locale: String!
	}
	`)
	createTypes(`
	interface ContentfulReference {
	contentful_id: String!
	id: ID!
	}
	`)

But if someone uses Entry or Reference in Contentful model names - they cause conflicts with those internal plugin types (because in the contentful plugin those model names are also transformed to ContentfulEntry and ContentfulReference).

So this is a conflict on a plugin level - Gatsby doesn't restrict type names (as long as they are prefixed with Contentful). So I think for list-based exceptions you can just go with Reference and Entry (and whatever other internal type names the plugin has). Alternatively, you can rename plugin interface types to something else, e.g. InternalContentfulReference (but that will be a breaking change).

Originally posted by @vladar in #29446 (reply in thread)

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜