v4.0.0

• Updated @apollo/federation dependency for Node 18 compatibility.
• Minimum version support is now node 18

v3.1.0

What's Changed

Uses a newer graphql-tools dependency : #99

New Contributors

• @logovaser made their first contribution in #99

Full Changelog: v3.0.4...v3.1.0

v3.0.4

Updating prune function from latest graphql-tools and updates the TS types for accuracy.

v3.0.3

Merge imported directives into final schema.

v3.0.2 Update

Full Changelog: v3.0.1...v3.0.2-fixed

V3.0.1

What's Changed

• accept a config where exclude is not defined by @tlivings in #93

Full Changelog: v3.0.0...v3.0.1

v3.0.0

Upgraded graphql-tools to improve schema merging.

v2.2.0

• [FEATURE] - Add "hook" for custom makeExecutableSchema function

v2.1.7

[FIXED] - Explicitly removed wrapping of the federation __resolveReference() resolver which was preventing __resolveReference() from running when using graphql-component to build federated schemas in seperate graphql services.

v2.1.6

• [FIXED] - A bug with graphql-component being used in a federated schema was brought to our attention and was attributed to the non-root type field resolver wrapping performed to help prevent double execution of resolvers with local delegation. Effectively, the resolver wrapping functionality was causing a null value to be returned (by attempting to return a value from the root arg) when the wrapper should have been calling through to the actual resolver. To fix this, separate wrapper functions are used for fields that begin with __ (such as __resolveType()) versus "normal" non-root type fields. These separated wrapper functions look for similar but slightly different conditions to determine whether to "short circuit" an already computed result which ensures that the wrapper functions are short circuiting or calling through to the actual resolver in the desired situations.