Image field validation does not work if sub-fields are valid about sanity HOT 3 CLOSED

@jordanl17 ah thanks, I missed that in the docs 😅

from sanity.

Hi eliasm307 thank you for reporting and all the details added.

We can reproduce it internally and the bug has been added to triage, we will keep this issue updated once it's fixed.

from sanity.

Hello,

You are facing this issue as validation: (Rule) => Rule.required() will only check for any value. Specifically, for validity of an image or file field, an asset must be present to be considered defined. Please update the validation on the mainImage as below:

import type { FieldDefinition } from "sanity";

export const MainImageField: FieldDefinition<"image"> = {
  name: "mainImage",
  title: "Image principale",
  type: "image",
  validation: (Rule) => Rule.required().assetRequired(), // specifically require field value to have an asset assigned
  fields: [
    {
      name: "alt",
      type: "string",
      title: "Texte alternatif de l'image",
      validation: (Rule) => Rule.required(), // sub-field is also required
    },
  ],
};

See more details here

from sanity.