Bad rendering of of multipart/form-data file example about api-console HOT 3 CLOSED

@egiraudy thanks for the request.

I wonder what the expected behaviour for this is for non .json files. Other examples are rendered as text because their content-type is known beforehand, but for parameters of type file, there really is no way to know the content-type, so any set rendering will be always wrong for some file types.

I believe that it would be a good addition to the RAML spec adding a content-type field (which should be an array) or similar way to specify the type of files, and then, the console for known types could use the rendering you propose.

from api-console.

@dmartinezg I already suggestion this addition to the spec ;-)
see http://forums.raml.org/t/documenting-multipart-form-data-file-format/343

from api-console.

API Console version 3 is no longer supported. We are at version 6 right now.
Please, upgrade your version of the console to have latest updates.

from api-console.