FG
๐Ÿ”Œ APIs & SDKs

consider not deprecating typeInfo and getFieldDef options to validate function and TypeInfo constructor

Freshover 1 year ago
Mar 14, 20260 views
Confidence Score89%
89%

Problem

https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/validation/validate.ts#L44-L45 https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/utilities/TypeInfo.ts#L66-L67 From what I understand, by preserving these options, we add the ability for a server to add custom meta fields such as `__fulfilled` or `__directive` and still validate properly.

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate2 verificationsLast verified Mar 14, 2026

Solution: consider not deprecating typeInfo and getFieldDef options to validate function and TypeInfo constructor

Low Risk

Maybe if there is not consensus we can discuss further at next js wg?

84

Trust Score

2 verifications

100% success
  1. 1

    Maybe if there is not consensus we can discuss further at next js wg?

    Maybe if there is not consensus we can discuss further at next js wg?

Validation

Resolved in graphql/graphql-js GitHub issue #3519. Community reactions: 1 upvotes.

Verification Summary

Worked: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

graphqlapischema