What defines an Astro content type

[Jean-Baptiste-Lasselle]

It's very clear, it is collections, or more precisely cwhat astro calls "content collections" :

https://docs.astro.build/en/guides/content-collections/

there also is the equivalent of hugo's draft: true : if the content file name begins with an underscore, it is excluded from the astro build.

[Jean-Baptiste-Lasselle]

[Jean-Baptiste-Lasselle]

Now very important, from an example :

Above :

• we define a collection using the defineCollection astro utility
• we define the Schema which will constraint the frontmatter of the entries in the collection
• and the last part, called registering the collection, is about tying up the typescript created object blogCollection, to the src/content/blog folder
• and all that in the src/content/config.ts file, which is looked up by the astro build: astro expects an src/content/config.ts file.
• In other words: the collections defined in src/content/config.ts are one to one associated with src/content subfolders, and for each collection defined in src/content/config.ts, the schema defined using zod, a typescript interface is generated in the .astro/types.d.ts

So basically, if i want pesto to generate Content Types for Astro, I need to be able to generate a Zod Schema, from a typescript interface :

• the user defines a typescript interface, in the UI (the UI guides him, and also restrictis him, to limit the complexity of the typescript interface)
• the typescript interface is saved into the database
• pesto generates the zod schema for the astro content collection , and edits the src/content/config.ts to update it
• and finally, the pesto UI uses the typechecking (zod or interface) to generate the form, to edit the frontmatter of the markdown

So basically, the question is about generating a zod schema from a not too complex typescript interface, and apprently, that's possible according the very interesting issue https://github.com/colinhacks/zod/issues/53

see also https://transform.tools/typescript-to-zod