DOCUMENTATION / RULE REFERENCE

Request property becomes required.

By Soumik Ghosh ยท Published

An existing caller can omit a field that the revised request requires. Supply a value based on application intent and validate the complete request.

Rule ID
request.now_required
Direction
request
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": {
    "name": {
      "type": "string"
    }
  }
}

After

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

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.

API compatibility guides and tools

Rule reference