1 / 5
Fill in: 'We ___ new fields as nullable so old clients don't break.'
-
-
-
-
We 'add fields' — the standard, simple collocation for extending a schema. The other options aren't idiomatic here.
2 / 5
Fill in: 'We ___ a field before removing it so consumers have time to migrate.'
-
-
-
-
We 'deprecate a field' — the standard GraphQL collocation for marking it for removal. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ query complexity to stop a single request overloading the resolver graph.'
-
-
-
-
We 'limit complexity' — the standard collocation for capping expensive queries. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ resolver usage so we know which fields are safe to remove.'
-
-
-
-
We 'track usage' — the standard collocation for monitoring which parts of the schema are consumed. The other options are less idiomatic here.
5 / 5
Fill in: 'A breaking schema change will ___ any client still querying the old shape.'
-
-
-
-
We say a change will 'break' a client — the standard collocation for causing a failure. The other options aren't idiomatic here.