1 / 5
Fill in: 'We ___ the OpenAPI schema directly from route handler annotations so the spec never drifts from the actual code.'
-
-
-
-
We 'generate a schema' — the standard, simple collocation for producing a spec from source. The other options are less idiomatic here.
2 / 5
Fill in: 'A hand-written spec kept separate from the code can ___ endpoints and docs quietly falling out of sync.'
-
-
-
-
We say a manually maintained spec will 'leave' things out of sync — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the generated schema against the live API in CI so a breaking change gets caught before release.'
-
-
-
-
We 'validate a schema' — the standard, established collocation for verifying a spec is accurate. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ client SDKs automatically from the OpenAPI schema instead of hand-writing request wrappers per language.'
-
-
-
-
We 'generate SDKs' — the standard, established collocation for producing client code from a spec. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ deprecated fields in the schema clearly so consumers get a warning well before removal.'
-
-
-
-
We 'mark' a field — the standard, simple collocation for flagging deprecated status. The other options are less idiomatic here.