Practise the standard verbs for deprecating a GraphQL schema field gracefully.
0 / 5 completed
1 / 5
Fill in: 'We ___ an old field with @deprecated and a reason, rather than removing it outright and breaking every actual client at once.'
We 'mark a field' — the standard, simple collocation for deprecating a GraphQL schema field gracefully. The other options are less idiomatic here.
2 / 5
Fill in: 'Removing a field with no deprecation notice can ___ every client on the old query throwing errors overnight.'
We say an abrupt removal will 'leave' clients throwing errors — the standard, natural collocation for the resulting breakage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a sunset date in the deprecation reason string, rather than a vague warning nobody can actually plan a migration around.'
We 'state a date' — the standard, simple collocation for specifying when a deprecated field will be removed. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ query logs for the deprecated field's actual usage, rather than removing it while clients are still actively querying it.'
We 'check logs' — the standard, simple collocation for confirming a deprecated field's remaining usage before removal. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every consuming team before the actual removal date, rather than letting a schema change surprise a client nobody's actually notified.'
We 'notify a team' — the standard, simple collocation for warning consumers of an upcoming schema removal. The other options aren't idiomatic here.