DOCUMENTATION / RULE REFERENCE

Response property removed.

By Soumik Ghosh · Published 3 November 2026

The revised response no longer promises a property used by existing consumers. Inspect field reads and missing-value behavior; a cast alone is not a runtime check.

Rule ID

response.removed

Direction

response

Classification

Breaking

What does a minimal example look like?

These are illustrative JSON Schemas for the changed constraint, not a captured vendor release. The rule ID applies to detector findings with the relevant direction and policy context.

Before

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

After

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

What should I check in my application?

Find the operation and affected field in the scanned commit. Confirm the server policy and application intent, inspect any missing coverage, then test the complete candidate. This rule alone does not prove repository impact, runtime failure, or a safe automatic fix.

Replay classifier inputs and policy choices or compare these schemas in both directions.