Security on nested routers

[ghost]

Reading the Swagger Bearer Authentication documentation, it is possible to add security globally, or on a specific route or routes (e.g. in the /private routes in the below screenshot.)

This doesn't appear to apply to a nested router such as the Secure section below. This nested router includes the security configuration as part of the schema but is seemingly ignored as no lock appears on the route, nor is security listed in the openapi.json for those routes (unlike the /private routes.)

Is (the inability of) applying security to all routes inside a nested router a limitation of itty-router-openapi, OpenAPI itself, or am I perhaps going about this the wrong way?

Repository: https://github.com/jasiqli/itty-openapi-security-test

[G4brym]

Hey @jasiqli thanks for submitting this bug report, we are planning a big upgrade and will make sure to include this