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.
From #59, it seems like the best option is to allow the ability to no-op packages while executing schema extraction.
The config might look like this:
import{SanityCodegenConfig}from'sanity-codegen';constconfig: SanityCodegenConfig={// 👇 this will prevent errors from importing this package during schema extractionignorePackages: ['sanity-plugin-tabs'],// ...};exportdefaultconfig;
This issue is a todo item for myself.
The text was updated successfully, but these errors were encountered:
* Export props and component for use in ErrorLayout
* Created Layout for Error pages
* Created 404 and 500 pages
* Changed contact us slug
* Injects styled component styles into header for SSR
One issue with this approach is that if you're no-oping a package that's used in generation of a type, you can't then use any functions from that package. eg, with orderable-document-list:
Which then results in the Cannot convert object to primitive value thrown from validatePropertyName because the sanityTypeName is indeed a function, and it can't be called to resolve it because it's no-op 😢
From #59, it seems like the best option is to allow the ability to no-op packages while executing schema extraction.
The config might look like this:
This issue is a todo item for myself.
The text was updated successfully, but these errors were encountered: