xuorig / chromatophore

GraphQL Continuous Evolution

Marc-Andre Giroux

chromatophore's Issues

Could this work better with a code first approach?

Cool idea! Have you thought about implementing this in a code-first approach instead of schema-first?
E.g. allow the developer to "overload" a resolver with a version tag (or similar).
The client can send a Version Header (or similar) if they want to pin it to an old version.
Oops, we're introducing versioning to GraphQL...

So, with a code-first approach, you don't have to create priceV2, priceV3, etc.. and no additional directives are required, just implement multiple resolvers, deprecate the old ones, but keep old resolvers existent to not break old clients.