At a glance
- Identifier: #1040
- Stage: RFC 3 / Accepted
- Champion: @martinbonnin
- Latest activity: Added to WG agenda on 2024-12-05
- Spec PR: https://github.com/graphql/graphql-spec/pull/1040
- Related:
Spec PR description
Follow up from https://github.com/graphql/graphql-spec/issues/53#issuecomment-1688335159
Make reason non-nullable:
directive @deprecated(
reason: String! = "No longer supported"
) on FIELD_DEFINITION | ARGUMENT_DEFINITION | INPUT_FIELD_DEFINITION | ENUM_VALUE
This is technically a breaking change for someone that does this:
type Foo {
bar: String! @deprecated(reason: null)
}
But feels like this shouldn't be allowed in the first place?
Fixes https://github.com/graphql/graphql-spec/issues/53
Timeline
- Added to WG agenda on 2024-12-05
- Mentioned in WG notes on 2024-12-01
- 2 commits pushed on 2024-11-22:
- martinbonnin committed "update language for deprecationReason"
- martinbonnin committed "add missing bang"
- Added to WG agenda on 2024-11-07
- Spec PR created on 2023-08-23 by martinbonnin
- Commit pushed on 2023-08-23 by martinbonnin: Make the reason argument in
@deprecatednon-nullable