We never tried to support that.

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

+1

Also, currently if you want to define specific example and description for each query parameter, you have to define multiple schemas and pass them to blp.arguments separately. With the above feature, all these schema definitions would be eliminated.

@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?

class QueryArgsSchema(ma.Schema):
    arg1 = ma.fields.String(metadata={"description": "First arg", "example": "Example value})
    ...

+1 for this feature.
Although, for reference, you can use @blp.arguments(ma.Schema.from_dict({'name': ma.fields.Str()}))

I've been trying to take over #423. The issue with from_dict is that the generated schema has a default name ("Generated") and apispec complains that Multiple schemas resolved to the name Generated.

I see no simple way to infer a better name.

There is no point adding a schema_name . At this point, the user might as well do

@blp.arguments(ma.Schema.from_dict({'name': ma.fields.Str()}, name="MeaningfulSchemaName"))

or even create a schema the normal way.

We could use a unique name generator, for instance using a global counter and use it when we build the schemas from dict. I don't really like the sound of it but I suppose users using dicts for schemas don't really care about the name.