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

allow type resolution with GraphQLObjectTypes #117

Merged
merged 1 commit into from Dec 20, 2021

Conversation

yaacovCR
Copy link
Owner

@yaacovCR yaacovCR commented Dec 19, 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.

@changeset-bot
Copy link

changeset-bot bot commented Dec 19, 2021

⚠️ No Changeset found

Latest commit: 38c586d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@yaacovCR yaacovCR force-pushed the allow-resolve-as-object-type branch 3 times, most recently from 94d785a to a8faf3f Compare December 20, 2021 16:05
...as opposed to just type names.
@yaacovCR yaacovCR merged commit 0b6363a into main Dec 20, 2021
@yaacovCR yaacovCR deleted the allow-resolve-as-object-type branch December 20, 2021 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant