Jérôme Lafréchoux

I reworked the doc paragraph to only provide a SQLAlchemy example that should work out-of-the-box.

Maybe the `Upload` field doesn't yield the proper documentation. I'm open to suggestion about how to improve/fix this if it is the case. It might be interesting to also try...

OpenAPI 2 is quite different and although I never heard of a deprecation date, I'd be reluctant to push for its use. However, there are slight differences in v3.0.x and...

You may want to double-check the marshmallow versions are the same, and perhaps the webargs versions too. -- Jérôme

Never heard of it. No objection if it can be supported as easily as the other front-ends (can options be passed as dicts like Swagger-Ui or Rapidoc config?). PR welcome...

We most often deploy with nginx + uwsgi and setup uswgi to prepend API URLs with `/api/v1` like explained [here](https://uwsgi-docs.readthedocs.io/en/latest/Snippets.html#multiple-flask-apps-in-different-mountpoints). I believe this is transparent to Flask so we don't...

Oh, I get it. Your resources involves many query arguments and you want to use `POST` to pass them in body instead. I don't think there's anything preventing the use...

Thank you guys for tackling this. I support the use case and in fact I'd be happy to close that long standing issue. I can't look at it right now....

Thanks for the contribution and sorry for not answering any sooner. Please allow me a little time to give this the attention it deserves. (Don't worry about test coverage at...

I think I get the point. But it's not clear to me what it allows that can't be done without it. Admittedly, documenting a security decorator is something users have...