This rule checks to ensure a
paths definition does not contain a Query string.
The mistake is actually quite common with authors new to the OpenAPI standard. It happens all the time.
Why did this violation appear?
One or more
paths definitions contains a query string.
paths: /deserts/icecream?sprinkles=true: get: parameters: ...
paths: /deserts/icecream: get: parameters: - in: query name: "sprinkles" ...
How do I fix this violation?
Ensure there are no query parameters ‘?key=value’ defined as a part of any
The rule is equivalent to path-not-include-query