Deprecate and remove std/mime/multipart

[lucacasonato]

We have FormData that has all the same functionality as std/mime/multipart as far as I can tell.

Let's deprecate this module for 1.18, and remove it for 1.19.

[jd1378]

How do we handle multipart on server side with FormData ?
Currently I use MultipartReader from std/mime/multipart to get the form data sent by a client. so how is this done with FormData if we remove this module ?
Please correct me if I'm missing something here

[lucacasonato]

You call Request.form on the incoming request. This will give you a Promise<FormData>

[jd1378]

It was request.formData, and it worked nicely, and It's a lot cleaner now, thanks !

[kidonng]

What's the current plan of deprecation, now that Deno 1.20 has been released? Should we still prepare the deprecation in next version (1.21) and remove it later, or just drop it now?

[kt3k]

I think we should still deprecate on the next version and remove it one minor version later

[bartlomieju]

Let's keep this issue open, until the module is removed.

[ry]

How do you write multipart data using FormData?

[lucacasonato]

@ry How do you write multipart data using FormData?

const form = new FormData();
form.set("foo", "bar");
const req = new Request("https://google.com", { body: form });

[elixiao]

How to parse form-data when I have a boundary string and multipart string/buffer？

[0f-0b]

How to parse form-data when I have a boundary string and multipart string/buffer？

Create a Response object with the content-type header set to `multipart/form-data; boundary=${yourBoundaryString}`, and call its formData method. formData returns a promise that either fulfills with a parsed FormData object or rejects with a TypeError.