Skip to content

Comments

validation: align MaxIntrospectionDepthRule with v16 backport#4583

Merged
yaacovCR merged 1 commit intographql:nextfrom
yaacovCR:next-max-introspection-depth-backport-parity
Feb 20, 2026
Merged

validation: align MaxIntrospectionDepthRule with v16 backport#4583
yaacovCR merged 1 commit intographql:nextfrom
yaacovCR:next-max-introspection-depth-backport-parity

Conversation

@yaacovCR
Copy link
Contributor

@yaacovCR yaacovCR requested a review from a team as a code owner February 20, 2026 09:10
@yaacovCR yaacovCR added the PR: bug fix 🐞 requires increase of "patch" version number label Feb 20, 2026
@vercel
Copy link

vercel bot commented Feb 20, 2026

@benjie 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 yaacovCR merged commit 0e09439 into graphql:next Feb 20, 2026
16 of 17 checks passed
@yaacovCR yaacovCR deleted the next-max-introspection-depth-backport-parity branch February 20, 2026 09:23
if (
node.kind === Kind.FIELD &&
// check all introspection lists
// TODO: instead of relying on field names, check whether the type is a list
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should restore this TODO (or implement it), otherwise newly added list fields in introspection will bypass the list depth limits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: bug fix 🐞 requires increase of "patch" version number

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants