request-parameter-pattern-changed
Request parameter pattern changed.
directionrequestareaparameterskindconstraintsactionchange
Potentially breaking (level: warning)
oasdiff reports this as a warning: it breaks clients only in some cases, so it is surfaced for review rather than failing CI outright.
Change its severity or ignore it
To change the severity oasdiff assigns to request-parameter-pattern-changed, list its id and a level in a severity-levels file, one rule per line. The level can be err, warn, or info, or none to disable the check entirely:
# severity.txt
request-parameter-pattern-changed errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txtSetting the level to none disables the check, so it is no longer reported at all.
Related parameters rules
- new-optional-request-default-parameter-to-existing-path
- new-optional-request-parameter
- new-request-path-parameter
- new-required-request-default-parameter-to-existing-path
- new-required-request-header-property
- new-required-request-parameter
- request-header-property-became-enum
- request-header-property-became-required