v0.2.0

Contact us here for help, more necessary open source tools and Enterprise support
or Chat with us on discord

BREAKING CHANGE
We dropped @graphql-mesh/transform-extend and introduce additionalTypeDefs because typeDefs and resolvers that do stitching must be provided with stitchSchemas if we want to benefit from selectionSet feature of GraphQL Tools Schema Stitching

{ 
   selectionSet: `{ id }`,  //<< ID should be available here even if the parent selection set doesn't have that.
   resolve ({ id }, { Users }) {
      return Users.api.user({ id }); 
   }
}

When we use extend transform and additionalResolvers, stitchSchemas doesn't understand they're stitching typeDefs and resolvers so selectionSet isn't applied there.

Related #301

You can check the examples of new usage;

• Schema Stitching -> https://github.com/Urigo/graphql-mesh/tree/master/examples/json-schema-covid
• Apollo Federation -> https://github.com/Urigo/graphql-mesh/tree/master/examples/federation-example