At a glance
- Identifier: #1142
- Stage: RFC 3 / Accepted
- Champion: @martinbonnin
- Latest activity: Spec PR merged on 2025-05-01
- Spec PR: https://github.com/graphql/graphql-spec/pull/1142
- Related:
Spec PR description
- graphql-js PR: https://github.com/graphql/graphql-js/pull/4354
In the same spirit as https://github.com/graphql/graphql-spec/pull/1040, make includeDeprecated non-nullable in the introspection schema.
I don't think there is ever a reason to passe includeDeprecated: null?
Timeline
May 2025
- Spec PR merged on 2025-05-01 by leebyron
- Advanced to RFC 3 on 2025-05-01 by leebyron
- Added to WG agenda on 2025-05-01
April 2025
- Advanced to RFC 2 on 2025-04-03 by leebyron
- Added to WG agenda on 2025-04-03
March 2025
- Top comment edited on 2025-03-06 by martinbonnin
- Advanced to RFC 2 on 2025-03-06 by leebyron
- Added to WG agenda on 2025-03-06
- Spec PR created on 2025-03-04 by martinbonnin
- Top comment edited on 2025-03-04 by martinbonnin
- @martinbonnin committed "make `includeDeprecated` non nullable" on 2025-03-04