Vladimír Gorej
Vladimír Gorej
I can verify this is still manifesting in current version of 3.10.1.
Let's introduce backward compatible behavior: **ignore invalid http verbs in the spec**
Hi @andrzej-erli, I'm not able to reproduce what your setting. **Steps To Reproduced** I've used: 1. Open https://editor.swagger.io/ 2. Use following definition ```yaml openapi: 3.0.1 info: title: OAS2 response examples...
I'm closing this for now as there's been no follow up from the @andrzej-erli
Hi everybody, IMHO this is not something that is fixable. From security reasons it is just not technically possible to set the `Cookie` header. But if you face this issue,...
~~This still doesn't work correctly. E.g. when we reference `Errors` schema, only this schema is included in generated swagger, but we don't know how `Error` schema look like, because from...
The only workaround so far I could come up with is not using nested resources, but rather define urls in router statically and use defdelegate to keep backward compatibility with...
@mbuhot thanks. Only problem with this solution is the following: If I have a module with `swagger_definitions_common` function that returns common schema definitions, it is not possible to reference schema...
@mbuhot I've attached as PR with documentation about extracting common schemas. If you have a time, please have a look at it.
Tests are failing on x86 Platform, but pass on x64. Have no idea why thought.