-
Notifications
You must be signed in to change notification settings - Fork 194
Support referencing TS type definitions for type: 'json'
fields
#26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Is there any sense of what would be needed for this? Is it something a drive-through contributor could take care of? |
Thanks for your question @essential-randomness. Unfortunately I think this is part of some medium-to-large iteration on the current schema/typing-system and thus not a good candidate for any "drive-by contribution". Please leave a 👍 in the main comment though to express your "demand". :) |
Done! Is there anywhere to go to better understand the future iteration of the schema/typing system that you envision? There are some project I have in mind that where contentlayer would be helpful (mostly so I don't have to reimplement typed MDX + the build pipelines myself :P), but I'd like to have a clearer picture of where you want to be when you reach 1.0 before I start building on top of your work. |
In some cases where you're using
type: 'json'
you'd like to reference some existing TS type definitions instead of theany
type that's currently used forjson
fields. This applies to both regularfields
andcomputedFields
.Example:
Rough API idea:
Notes
The text was updated successfully, but these errors were encountered: