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.

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

resolveType: remove support for returning GraphQLObjectType #2905

Merged
merged 1 commit into from Feb 1, 2021

Conversation

IvanGoncharov
Copy link
Member

No description provided.

@IvanGoncharov IvanGoncharov added the PR: breaking change 💥 implementation requires increase of "major" version number label Feb 1, 2021
@IvanGoncharov IvanGoncharov merged commit dc89262 into graphql:main Feb 1, 2021
@IvanGoncharov IvanGoncharov deleted the pr_branch branch February 1, 2021 14:43
IvanGoncharov added a commit to IvanGoncharov/graphql-js that referenced this pull request Feb 20, 2021
IvanGoncharov added a commit to IvanGoncharov/graphql-js that referenced this pull request May 24, 2021
@boetersep
Copy link

The documentation was not updated

@saihaj
Copy link
Member

saihaj commented Dec 13, 2021

@boetersep yeah we are running very behind on apps. We have a new site which should be landing soon which provides TS Docs api #3269

yaacovCR added a commit to yaacovCR/graphql-executor that referenced this pull request Dec 20, 2021
...as opposed to just type names.

This reverts graphql#2905

This change was made upstream to support schema transformation functions like lexicographicallySortSchema which do not modify resolveType methods. Previously, a workaround was included that simply looks up the actual type from the type name returned by resolveType. In actuality, in my opinion, the schema transformation functions should natively or manually modify the resolveType function so it works correctly.

In any case, we restore the workaround here to preserve v14 support.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: breaking change 💥 implementation requires increase of "major" version number
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants