v1.3.0

• Resolver memoize key includes the info.path.key to keep different aliases from colliding
• Imported resolvers will delegate to the imported component schema to which they belong.
• Remove this._context as default value for context in execute() requiring execute() users to pass in context from a calling resolver.
• Remove binding of GraphQLComponent class context to Subscription resolvers.
• Apply proxyImportedResolvers regardless of how the way a component is imported and whether or not exclusions are provided. proxyImportedResolvers can still be turned off for an imported component if the component is passed via config object.

v1.3.0-rc2

• Resolver memoize key includes the info.path.key to keep different aliases from colliding
• Imported resolvers will delegate to the imported component schema to which they belong.
• Remove this._context as default value for context in execute() requiring execute() users to pass in context from a calling resolver.
• Remove binding of GraphQLComponent class context to Subscription resolvers.
• Fixed proxyImportedResolvers option to include exclude scenario

v1.3.0-rc1

• Imported resolvers will delegate to the imported component schema to which they belong (see below).
• Remove this._context as default value for context in execute() requiring execute() users to pass in context from a calling resolver.

When a component imports another component, it imports the types as well as both root and type resolvers. If the parent component is utilizing execute, type resolvers will run twice because the sub-component will execute type resolvers to complete query and the parent component, which has imported the type resolvers will rerun them when it encounters the type.

This change keeps type resolvers from being imported and replaces imported root type resolvers with resolvers that delegate to the imported component schema as a sub-query.

There is a flag to disable this default behavior.