**API Platform version(s) affected**: 4.1.15 <!-- Warning: if your version is 2.7 we ask you to try the 3.0 version. If the bug is present there we will fix it. If the bug is due to old 2.6 behavior we can't fix it. In that last case we recommend to either upgrade to 3.0 or to temporarily replace concerned service with your own. --> **Description** Some spec readers will throw an error on `allowEmptyValue` as its present on a path parameter when the spec says: > This field is valid only for query parameters. Use of this field is NOT RECOMMENDED, and it is likely to be removed in a later revision. You can't remove the parameter using the decorator either I don't think. ` "parameters": [ { "name": "code", "in": "path", "description": "GiftCard identifier", "required": true, "deprecated": false, "allowEmptyValue": false, "schema": { "type": "string" }, "style": "simple", "explode": false, "allowReserved": false } ], ` **How to reproduce** Appears on all path parameters I've created so far.