Skip to main content

operation-parameters-unique

Requires each name + in pair to be unique within path-level and operation-level parameter arrays.

AttributeValue
CategoryParameters
MaturityBaseline
StarterWarning
Lenient–CompleteError

Intent

Duplicate parameter identities are ambiguous for validators, generators, and callers.

See it fail

parameters:
- { in: query, name: status, schema: { type: string } }
- { in: query, name: status, schema: { type: string } }

Same name in different locations, such as query and header, is allowed.

Fix it

Keep one definition or give each parameter a distinct identity.

Configure under profiles.<name>.rules.override.operation-parameters-unique.

Nearby: query-param-collision, path-params-defined.