Open bmle69 opened 4 months ago
@bmle69 I've checked the spec and that name
field should indeed not be there.
What validator are you using to check this? Thinking if we should add it to our CI.
Hi @provinzkraut , this is the one I'm using: https://pypi.org/project/openapi-spec-validator/
I'm seeing some other examples of the generated openapi doc from litestar failing to validate. Let me know if you want me to file separate tickets or just keep it in this one.
Description
Hi, I'm having some issues with validating the openapi specs outputted by Litestar and not sure where to start. I'd like to build in a validator to validate the spec in order to make these apis publicly available as part of my CI/CD flow. Here's a simple example that doesn't pass validation just from adding BearerToken as a security scheme. In this case, the
name
key inBearerToken
is the issue and removing it from the spec allows it to pass validation.This is being generated by this Litestar app:
And with using the validator, I'm getting this error:
URL to code causing the issue
No response
MCVE
Steps to reproduce
Screenshots
Logs
No response
Litestar Version
2.9.1
Platform