Hi Steve,
My message is probably wrong!
As far as I can remember, the miss was not in Colander documentation, but
in Cornice Swagger extension documentation about types converters
registration; an issue is already open to add this to it's documentation...
Best regards,
Thierry
--
On 2/9/21 12:56 AM, Thierry Florac wrote:
> I found that Colander is probably lacking a few documentation about creating
> and registering custom types and converters
I'd like to improve the docs. Would you please open an issue with what you
think is missing from this section?
Hi Michael,
I finally made my REST API service to accept both multipart/form-data and
JSON base64 encoded data...
Implementation is probably not "perfect" (I found that Colander is probably
lacking a few documentation about creating and registering custom types and
converters), but at least it
To me it just kind of depends on what level of atomicity you need in your API
endpoint. If you can accept the binary data without any other parameters then
that's great, just do that. If you need it alongside other input then multipart
is great. Some people also marshal that stuff in x-foo
Hi,
I'm starting to use Cornice, Colander and Swagger and I'm trying to create
a REST service which should allow users to upload file(s)...
Until now I'm using "multipart/form-data" encoding and it seems OK, but :
- is it actually a good practice to handle file uploads in a REST API
using this
