[2022-11] if a field is deprecated on a type, it must be deprecated on the interface

[benjie]

Does this rule already exist? Should it?

Matt: do we have the rule that if a field is deprecated on a type then it must also be deprecated on any interface?
Lee: good question
Ivan: no, we don't have this rule.
Stephen: sounds like another PR; it probably should - right?
Lee: yeah, it's surprising that hasn't come up in the Facebook API.
Matt: interface fields tend to be Hack/PHP; everyone gets the same implementation (same code executed) - deprecating it deprecates it everywhere.
ACTION - validate this.

• assignee(s): unknown
• source: https://github.com/graphql/graphql-wg/blob/main/notes/2022/2022-11.md#deprecated-on-object-15m-stephen

---

Note: Action Item issues are reviewed and closed during Working Group
meetings.

[benjie]

Finally catching up with filing action items...

@mjmahone @fotoetienne Would either of you like to take this on?

[benjie]

Spec PR raised here: graphql/graphql-spec#1053

[benjie]

GraphQL.js PR raised here: graphql/graphql-js#3986

[benjie]

Added to next WG: #1429

[fotoetienne]

Amazing, thanks for doing this @benjie

[benjie]

PRs raised; closing 👍