You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
@sanity/document-internationalization
can add__i18n_lang
,__i18n_refs
and__i18n_base
fields to schemas withi18n
flag.But it's also possible to use custom names on both global or schema level:
![image](https://user-images.githubusercontent.com/113703456/227557398-353d4639-de74-43d8-9fbe-6a2bdef3e0ed.png)
Two options are in my mind
Like
The text was updated successfully, but these errors were encountered: