request-optional-property-became-write-only
Request optional property became write-only.
Not breaking (level: info)
oasdiff records this in the changelog but does not fail CI by default. Requests that were valid under the old contract are still valid, so existing clients are not affected.
What this check detects
`writeOnly` means a property is sent in requests but never returned in responses. Marking an optional request property write-only therefore does not change what clients may send, which is why it is informational.
The thing to check is the response side: if the same schema is also used for responses, that field stops being returned, and a client reading it back will now find it missing.
Example
Clients still send "apiKey" exactly as before. If this schema is shared with a response, the server no longer returns the field there.
Change its severity
oasdiff reports request-optional-property-became-write-only as informational, so it does not fail CI. To treat it as a warning or an error under your own compatibility policy, or to turn it off, set its level in a severity-levels file:
Put one rule per line; the level can be err, warn, or info, or none to disable the check entirely:
# severity.txt
request-optional-property-became-write-only errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt