different documentation instances based on blueprints

[AdamVerner]

My application employs multiple blueprints which i would like to generate separate documentation for.
I don't want the customers to see the endpoints i use in the internal frontend.

Currently i use workaround with DispatcherMiddleware so i can have multiple app instances, instead of using blueprints. That solution is really cumbersome and creates other issues with debugging, readability, extensions and so on. It would be nice to have option to have multiple endpoints based on Blueprints.

[reteps]

@greyli -- Is this a feature you would ever consider adding? This is a must-have for my project.

[reteps]

The closest equivalent to this feature I could find was this PR in flask-smorest.

[greyli]

Hi! I tried to implement this and managed to create the separate OpenAPI spec for different blueprints, but it needs a lot of code changes. I decided to move to the 2.1.0 version milestone.

[reteps]

Amazing, thank you!