Support for @sanity/document-internationalization

[sorokin-energi]

Hi,

@sanity/document-internationalization can add __i18n_lang, __i18n_refs and __i18n_base fields to schemas with i18n flag.

But it's also possible to use custom names on both global or schema level:

Two options are in my mind

1. try to support specifically this official plugin
2. try to support dynamic type extension (for instance with codegen option and something similar to openapi spec syntax)

Like

const type = defineType({
    name: 'myType'
    i18n: true,
    codegen: {
        extend: {
           __i18n_lang: { type: [String] },
           ...
        }  
    } 
})

[ochicf]

Ideas to handle this in v1:

• since the sanity config file is read by the package, it would be possible to know whether the document-i18n is in the plugins list
• from a quick look at the plugin object, I don't think the configuration for the plugin is exposed, so if the plugin is detected a possible behaviour could be:
  • try to read the documentI18n property from the sanity codegen config, and use the fieldNames property set there
  • if the above is not set, generate the default fields (and add a log explaining this fact to the user in case needs to be changed)

Then the generator would add the configured/default field names for schemas with i18n: true.