Catch Image.asset not found error

[surjithctly]

I'm getting the following error when we pass image.alt but not image.asset. This plugin should send appropriate error when image.asset is not found.

In my code, I cannot do the following because hooks cannot call conditionally.

// This won't work
// Not able to call hooks conditionally. 

  if (!image.asset) {
    return null;
  }
 const imageProps = useNextSanityImage(client, image, {
    imageBuilder: CustomImageBuilder
  });

[lorenzodejong]

Could you perhaps clarify in which scenario this occurs, preferably with a code example of how you retrieve the image from Sanity?

[lorenzodejong]

Closing due to inactivity, issue can be reopened if we can get a reproducible case.

[surjithctly]

Hey,

Sorry, missed your comment. It happens when "image" exists but not "image.asset". I had this issue when I added an image caption without adding image.

To Reproduce:

1. Go to Sanity and create an image field with caption / alt
2. Now fill the alt & caption, but don't upload any photo
3. Save & run the plugin
4. It will throw this error because the image does not have asset.

[surjithctly]

Now, I tried to add an exception in my code for this scenario.

 if (!image.asset) {
    return null;
  }

But now there is another error called: hooks cannot call conditionally.

So, I can't do this error exception in my code. So checking the possibility to check this in the plugin itself.

[lorenzodejong]

Just checked this in the Sanity studio which i use for testing purposes. It looks like i have to select/upload an image before the "Edit details" button becomes visible and i can specify a caption/alt. What does the configuration of your Sanity image field look like?

[surjithctly]

I have isHighlighted trueas per https://www.sanity.io/docs/image-type

So it will be visible all time.

  fields: [
    {
      name: 'caption',
      type: 'string',
      title: 'Caption',
      options: {
        isHighlighted: true // <-- make this field easily accessible
      }
    },

[lorenzodejong]

Thanks for the extensive example. I've just released version 3.1.7 which includes a check for the existence of the image id in order to fix this issue.