TypeGen define non-null for singletons in queries

[notflip]

I'm using the following query to fetch a few singletons

export const SETTINGS_QUERY = groq`
{
  "general": *[_type == "settings"][0] {
    email,
    "privacyPolicyPage": privacyPolicyPage->slug.current,
    "cookiePolicyPage": cookiePolicyPage->slug.current,
  },
  "socials": *[_type == "socials"][0] {
    "socialMediaLinks": socialMediaLinks[].url
  },
  "seo": *[_type == "seo"][0] {
    meta_title,
    meta_description,
    meta_image
  }
}
`

The types of settings, socials and seo are singletons in my Sanity Studio (so they will always be defined)

However when using TypeGen the result is

// Variable: SETTINGS_QUERY
// Query: {  "general": *[_type == "settings"][0] {    email,    "privacyPolicyPage": privacyPolicyPage->slug.current,    "cookiePolicyPage": cookiePolicyPage->slug.current,  },  "socials": *[_type == "socials"][0] {    "socialMediaLinks": socialMediaLinks[].url  },  "seo": *[_type == "seo"][0] {    meta_title,    meta_description,    meta_image  }}
export type SETTINGS_QUERYResult = {
  general: {
    email: string | null
    privacyPolicyPage: string | null
    cookiePolicyPage: string | null
  } | null
  socials: {
    socialMediaLinks: Array<string | null> | null
  } | null
  seo: {
    meta_title: string
    meta_description: string
    meta_image: {
      asset?: {
        _ref: string
        _type: 'reference'
        _weak?: boolean
        [internalGroqTypeReferenceTo]?: 'sanity.imageAsset'
      }
      hotspot?: SanityImageHotspot
      crop?: SanityImageCrop
      _type: 'image'
    } | null
  } | null
}

Each of these items can be null, according to typegen, which causes a lot of if-checks in my vue code. Is there a way to tell TypeGen that these are singletons/always defined?

This is an example of my singleton code for SEO

import {defineField, defineType} from 'sanity'
import {TextAreaInput} from '@/components/TextAreaInput'
import {SparkleIcon as Icon} from '@sanity/icons'

export default defineType({
  name: 'seo',
  title: 'SEO',
  type: 'document',
  icon: Icon,
  fields: [
    defineField({
      type: 'string',
      name: 'meta_title',
      title: 'Meta Title',
      validation: (rule) => rule.required(),
      description: 'Website titel voor de tab title, metadata en zoekmachines',
    }),
    defineField({
      type: 'text',
      name: 'meta_description',
      title: 'Meta Description',
      validation: (rule) => rule.required(),
      description:
        'Korte paragraaf voor zoekmachines, metadata en social sharing. Dit is een beknopte samenvatting die zoekmachines en gebruikers helpt te begrijpen waar de pagina over gaat, ideale lengte van tussen 70 en 160 karakters',
      components: {
        input: (props) => <TextAreaInput {...props} min={70} max={160} />,
      },
    }),
    defineField({
      type: 'image',
      name: 'meta_image',
      title: 'OG Image',
      description:
        'De afbeelding die wordt weergegeven wanneer de pagina op sociale media wordt gedeeld, wat de zichtbaarheid en aantrekkingskracht van de gedeelde link vergroot.',
    }),
  ],
})

[EricWVGG]

I believe the answer is yes, there is a way.

If you add this to your typegen command in package.json, it should do exactly what you want:

    "typegen": "sanity schema extract --enforce-required-fields && sanity typegen generate",

This of course only applies to items in schema where validation: rule => rule.required(). more here: https://www.sanity.io/docs/sanity-typegen#b076840a64df

Although I am curious as to why the entire result of your query isn't | null, it should be accounting for a possibility of "no result of query at all." Hm.

[EricWVGG]

oh, I just figured that last bit out, it's because I have drafts enabled.