Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move __resolveReference resolvers on to extensions #1746

Merged
merged 3 commits into from
Apr 20, 2022
Merged

Move __resolveReference resolvers on to extensions #1746

merged 3 commits into from
Apr 20, 2022

Commits on Apr 19, 2022

  1. Move __resolveReference resolvers on to extensions 

    The entity __resolveReference resolver is currently placed directly
on to GraphQL*Type objects. This breaks the API, as the expectation
is to put things like this on to the `extensions` field of objects
contained within a GraphQLSchema.

This moves the resolver off of the object and into the extensions
where it belongs.

Fixes: #1131
Fixes: ardatan/graphql-tools#2687
Fixes: ardatan/graphql-tools#2857
    @trevor-scheer
    trevor-scheer committed Apr 19, 2022
    Configuration menu
    Copy the full SHA
    7291f3d View commit details
    Browse the repository at this point in the history

Commits on Apr 20, 2022

  1. Nest extensions (and fix types accordingly)

    @trevor-scheer
    trevor-scheer committed Apr 20, 2022
    Configuration menu
    Copy the full SHA
    e504e27 View commit details
    Browse the repository at this point in the history

  2. Namespace with apollo.subgraph

    @trevor-scheer
    trevor-scheer committed Apr 20, 2022
    Configuration menu
    Copy the full SHA
    d4f7b7f View commit details
    Browse the repository at this point in the history