Behaviur when use files type parameters about apiflask HOT 5 CLOSED

The reason is if we don't select a file, swagger will send an empty value like this:

POST http://localhost:5000/images HTTP/1.1
Content-Type: multipart/form-data; boundary=---------------------------70636434840698183742419445910

-----------------------------70636434840698183742419445910
Content-Disposition: form-data; name="image"


-----------------------------70636434840698183742419445910--

Then apiflask get an empty string in the parameter image, and send 422 response to the client because a ValidationError("Not a valid file.") has occurred.

I‘m not sure if we should handle this case or it's a bug of swagger. @greyli

from apiflask.

After tests, it seems to be the default behavior of swagger(Not a bug). We should handle it ourselves.

from apiflask.

Because the File field has been migrated to flask-marshmallow, I can't resolve it directly.

I’ll fix it and add tests after this pr is merged and released.

from apiflask.

@uncle-lv Thansk for the fast reaction and fix the bug.

Now it's working fine :)

from apiflask.

@uncle-lv Well done! Thank you for the fix.

from apiflask.