You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Interface field NodeWithFeaturedImage.featuredImage expected but Page does not provide it.",
My specific use case is so the gatsby-source-wordpress does not spend 30 minutes sourcing 9000 MediaItem nodes that I don't need.
@TylerBarnes alternatively, is there a way to get gatsby-source-wordpress to entirely exclude the MediaItem type from sourcing. Setting type.MediaItem.exclude to true gives an error that it is not a valid option.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to deregister a type, specifically
MediaItem
so that no other types, such asPage
reference anyMediaItems
like inPage.featuredImage
.I've tried deregistering the fields like so:
but then I get errors such as:
"Interface field NodeWithFeaturedImage.featuredImage expected but Page does not provide it.",
My specific use case is so the
gatsby-source-wordpress
does not spend 30 minutes sourcing 9000MediaItem
nodes that I don't need.@TylerBarnes alternatively, is there a way to get
gatsby-source-wordpress
to entirely exclude theMediaItem
type from sourcing. Settingtype.MediaItem.exclude
totrue
gives an error that it is not a valid option.Beta Was this translation helpful? Give feedback.
All reactions