Allow to generate the openapi from the axum router without serving it

[slinkydeveloper]

Hi, I would like to be able to extract the specification generated by Router::route_openapi_specification without serving the contract, how can I do it? Could we split route_openapi_specification in two steps?

[Flowneee]

Hi. Currently you can do the same as route_openapi_specification https://github.com/Flowneee/okapi-operation/blob/master/okapi-operation/src/axum_integration/router.rs#L327, since necessary methods are public:

let mut routes = self.routes_operations().openapi_operation_generators();
let spec = openapi_builder
    .add_operations(routes.into_iter().map(|((x, y), z)| (x, y, z)))?   // don't even ask :)
    .generate_spec()?;

Could we split route_openapi_specification in two steps?

Maybe instead add method which will add routes from Router to provided OpenApiBuilder? Something like Router::add_routes(&mut self, builder: &mut OpenaApiBuilder.

I am currently trying to rewrite entire axum integration, if OpenApiBuilder stays I will definitely add this feature.

If someone willing, it could be added to current version

[slinkydeveloper]

@Flowneee any update on your refactoring of the axum integration? It would be nice to have this feature somewhat soon :)

[Flowneee]

I published a 0.3.0-rc1 version, which include

• refactoring
• update to axum 0.7

Check it out, feedback would be appreciated. I'm gonna keep this issue open for now until it is not released.

[muturgan]

generate a static openapi spec is a great feature