DOCUMENTATION / RULE REFERENCE

Request property removed, server strictness unknown.

By Soumik Ghosh · Published 3 November 2026

A removed request field can be tolerated or rejected by the server. Without an established unknown-field policy, ParityDiff leaves the classification ambiguous.

Rule ID

request.removed_unknown_strictness

Direction

request

Classification

Needs review

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": {
    "name": {
      "type": "string"
    }
  }
}

After

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

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.