Relation Field - When empty, throw an error on Gatsby about gatsby-source-graphcms HOT 7 CLOSED

I was able to hack a workaround using setFieldsOnGraphQLNodeType. I added the following to gatsby-node.js to map a coverImage: null to coverImage: { handle: '' }. Then instead of checking for a null coverImage or handle in React, I check for an empty string.

exports.setFieldsOnGraphQLNodeType = (
  { type, store, pathPrefix, getNode, cache, reporter },
  pluginOptions
) => {
  if (type.name === 'Post') {
    // allow null coverImage fields
    type.nodes = type.nodes.map(node => {
      if (node.coverImage === null) {
        node.coverImage = {
          handle: '',
        };
      }
      return node;
    });
  }
};

Messy, but seems to work until they fix this. I'm honestly surprised Gatsby doesn't already support nullable fields...

from gatsby-source-graphcms.

cc: @rdela

I believe this has to do with the fact that gatsby ignores empty nodes and doesn't create the type. I'll look into it later this week

from gatsby-source-graphcms.

Yes I think you can find people discussing this in Gatsby issues in relation to the WordPress and Contentful plugins if anyone is feeling intrepid.

from gatsby-source-graphcms.

saw those ones as well, they discuss directly on gatsby project issue tracking because the plugins themselves are maintained inside the core project codebase. But it looks being an issue with the plugins themselves, not from gatsby core, no?

from gatsby-source-graphcms.

It's more related to the way gatsby internally creates types, I believe. If the field is empty the type will not be created.

@rdela Can you share links to those issues so I can read up? Can't seem to find them.

from gatsby-source-graphcms.

@Redmega Here are a couple from a quick search
gatsbyjs/gatsby#3495
gatsbyjs/gatsby#2564

Edit couple more:
gatsbyjs/gatsby#2937
gatsbyjs/gatsby#2539

from gatsby-source-graphcms.

did you find how to handle this properly in the v2?

from gatsby-source-graphcms.