graphql is just one representation of your applications data, it shouldn't dictate your models.
I'm thinking about adding something that generates a model if it doesn't exist, but after its generated it becomes the users problem to keep it in sync.
> recipe for mistakes and drift between the schemas and those types.
The type system enforces there is no drift, it won't compile if its not perfect.
I'm thinking about adding something that generates a model if it doesn't exist, but after its generated it becomes the users problem to keep it in sync.
> recipe for mistakes and drift between the schemas and those types.
The type system enforces there is no drift, it won't compile if its not perfect.