Jérôme Lafréchoux

There's two issues - 1/ Parsing this query string format correctly. - 2/ Documenting it correctly 1/ is a webargs issue, so I'll transfer to webargs. You'll have to write...

Yeah I'm afraid so. I'm not sure where to stand, here. Having the API framework serve the doc with close to no effort is certainly practical. We always use it....

Great. I'm glad to hear that. You're not stealing anything. You're sharing what you did with the code, which is more than expected by the licence. Thank you for that....

I've been thinking of a huge refactor. 1/ Extract what's not flask-related into a separate lib (smorest, marshmallow-smorest,...). flask-smorest would depend on this, and this would open the door to...

For the record, about werkzeug and ASGI: https://github.com/pallets/werkzeug/issues/1322.

AFAIU, async werkzeug does not exist yet, does it? All I see is https://github.com/pallets/werkzeug/pull/1330. And once async werkzeug is out, wouldn't it be easier to make async flask?

More info about Flask async vs. Quart: https://flask.palletsprojects.com/en/2.0.x/async-await/. > When to use Quart instead > > Flask’s async support is less performant than async-first frameworks due to the way it...

We never tried to support that. I wouldn't mind adding this feature if it is not too hard to support.

@technolingo do you mind being more explicit (with an example)? Can't you pass a single schema with each field providing its example and description? ```py class QueryArgsSchema(ma.Schema): arg1 = ma.fields.String(metadata={"description":...

Hi. You could do ```py class Example (Schema): moo = fields.String() # Or whatever type @blp.route("/") class Demo (MethodView): @blp.arguments(Example, location='query') def get(self, args): return 'ok' ``` but I guess...