Pydantic classes as single source of truth

I am working on a project where the backend is a python application using weaviate and a next.js frontend to interact with the users.

I would like to mantain a single source for the data schema and am using pydantic classes for this purpose.

My application objects are a pydantic class and my weaviate collection is described by a class derived from it with the collection name and the embedding module as aded metadata.

I am using the same application object to generate the typescript interfaces from it.

I would ideally want to use that pydantic class to generate the weaviate collection definition and/or constrain/typecheck the weaviate queries.

Any good practices to suggest?

Happy 2025 to all.

1 Like

Hello and happy new year!

We should have direct support for this in the clients:

1 Like

Thank you. Take care.