Error [ValidationError]: "error" must be of type object

[nmampersand]

Hello! I am working on a project using Gatsby, Cloudinary, and Sanity and am running into the error with this plugin:

Failed to validate error [Error [ValidationError]: "error" must be of type object] {
  _original: {
    context: {
      sourceMessage: '[gatsby-transformer-cloudinary] Could not get metadata for undefined > undefined: undefined'
    },
    error: 'Unknown cloud_name',
    pluginName: 'gatsby-transformer-cloudinary',
    text: '[gatsby-transformer-cloudinary] Could not get metadata for undefined > undefined: undefined',
    level: 'ERROR',
    stack: [],
    docsUrl: 'https://gatsby.dev/issue-how-to'
  },
  details: [
    {
      message: '"error" must be of type object',
      path: [Array],
      type: 'object.base',
      context: [Object]
    }
  ]
}

I am only using images already in Cloudinary but have tried configuring it with and without my Cloudinary credentials and receive the same error.

My gatsby-config looks like:

plugins: [
...,
{
    resolve: 'gatsby-source-filesystem',
    options: {
      name: `images`,
      path: `${__dirname}/src/images/`
    },
  }, {
    resolve: `gatsby-source-cloudinary`,
    options: {
      cloudName: process.env.CLOUDINARY_CLOUD_NAME,
      apiKey: process.env.CLOUDINARY_API_KEY,
      apiSecret: process.env.CLOUDINARY_API_SECRET,
    },
  }, {
    resolve: 'gatsby-transformer-cloudinary',
    options: {
      cloudName: process.env.CLOUDINARY_CLOUD_NAME,
      apiKey: process.env.CLOUDINARY_API_KEY,
      apiSecret: process.env.CLOUDINARY_API_SECRET,
      transformTypes: [
        `CloudinaryMedia`,
        `CloudinaryAsset`,
        `SanityCloudinaryAsset`
      ],
    },
  }]

[nmampersand]

Note: when I do provide the Cloudinary config options to the plugin and run gatsby develop, it does successfully upload my local images to Cloudinary but still throws the above error.

[raae]

That is not a great error message, so we'll make sure to fix that - ie. a better error message.

However the problem seems to be that your SanityCloudinaryAsset GraphQL type does not have the required fields for the plugin to work. It needs at least the fields: publicId and a cloudName.

Could you go to your GraphiQL UI (typically http://localhost:8000/___graphql) and check the shape of SanityCloudinaryAsset?

[nmampersand]

Thank you! Hmm, it looks like it doesn't have a cloud name:

    {
          "name": "SanityCloudinaryAsset",
          "fields": [
            {
              "name": "_key"
            },
            {
              "name": "_type"
            },
            {
              "name": "public_id"
            },
            {
              "name": "resource_type"
            },
            {
              "name": "type"
            },
            {
              "name": "format"
            },
            {
              "name": "version"
            },
            {
              "name": "url"
            },
            {
              "name": "secure_url"
            },
            {
              "name": "width"
            },
            {
              "name": "height"
            },
            {
              "name": "bytes"
            },
            {
              "name": "duration"
            },
            {
              "name": "tags"
            },
            {
              "name": "created_at"
            },
            {
              "name": "derived"
            },
            {
              "name": "access_mode"
            },
            {
              "name": "_rawDerived"
            }
          ]
        }

[raae]

And the data is not in the shape required by this plugin (something I hope to make configurable in the future). You'll have to make your own nodes base on these nodes. I can give you an example of how to achieve this tomorrow (CET timezone).

[nmampersand]

That would be great, thank you!

[raae]

I made a question and answered it here: #215 and keeping this issue to reference when fixing the not optimal error message. Let me know if that works or not.

[github-actions]

🎉 This issue has been resolved in version 3.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 4.2.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀