Add support for Blueprint.route()

[DerManoMann]

While I am at it ...

The application I am working on makes extensive use of the blueprint route() method, so adding support for that in APIBlueprint would make a potential integration at lot easier.

Thanks for all the work!

[luolingchun]

APIBlueprint inherited from Blueprint, so i think you can use the route() method directly .

but it doesn't work for swagger...

[DerManoMann]

Yes, that is the point. I am not quite sure what the difference is between route() and individual methods like get(), but I suppose it should be possible to override it in APIBlueprint?
That would also avoid having to refactor in cases where an endpoint supports more than one HTTP methods...

[luolingchun]

This library focuses more on RESTful APIs and OpenAPI docs.

[DerManoMann]

I am sorry, this answer doesn't make sense to me. Why is that different for OpenAPI docs whether a route is registered my route() vs. get()? (As mentioned, I am not clear about the difference between the two, but both can server JSON, XML or whatever and can support different auth schemes...?)

[DerManoMann]

I did some more digging. The API docs state that get() is a shortcut for route() with methods=["GET"]
From: https://flask.palletsprojects.com/en/2.0.x/api/#flask.Blueprint.get

However, the library does not support using route(), so that is why I am asking.

[luolingchun]

We can make it for swagger. But if you specify two HTTP methods in route()(e.g. GET, POST), you'll get two API with same parameters in swagger，it feels weird.

I think get for query resources and post for created . Why don't we use get and post separately to make things easier?

[ghost]

Fair enough.