Revert "refactor buildResolveInfo into a lazy class (#4530)"#4553
Merged
yaacovCR merged 1 commit intographql:nextfrom Feb 11, 2026
Merged
Revert "refactor buildResolveInfo into a lazy class (#4530)"#4553yaacovCR merged 1 commit intographql:nextfrom
yaacovCR merged 1 commit intographql:nextfrom
Conversation
|
@yaacovCR is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Feb 10, 2026
…ResolveInfo class (graphql#4552)" See graphql#4553, the lazy ResolveInfo class would break users who wrap resolvers by spreading info.
yaacovCR
added
PR: breaking change 💥
Sadly, this would break existing users that resolver functions by spreading the info argument.
yaacovCR
force-pushed
the
revert-resolve-info-class
branch
from
46a87e2 to
08687ae
Compare
yaacovCR
added
PR: bug fix 🐞
yaacovCR
added a commit
that referenced
this pull request
Feb 22, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 22, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 23, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 23, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
Sadly, this would break existing users that resolver functions by spreading the info argument. BREAKING CHANGE: this PR changes `info.abortSignal` to `info.getAbortSignal()` => while `info` as a whole is not lazy, changing to a method allows us to maintain laziness at least with regards to the creation of the abort signal.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sadly, this would break existing users that resolver functions by spreading the info argument.
BREAKING CHANGE: this PR changes
info.abortSignaltoinfo.getAbortSignal()=> now thatinfoas a whole is not lazy, changing to a method allows us to maintain laziness with regards to the creation of the abort signal.