Alex Indigo
Alex Indigo
Hey, I'm not really sure I understand the question, do you mind to elaborate? Thanks.
I see. Thanks. Yeah, we don't consider `getHeaders` being public API. The main idea of the module is to be Nodejs representation of the browser built-in FormData, so "public" API...
I understand it might look "normal" for users of "isomorphic" part of the library. But for node only users it would look somewhat ridiculous. :) I think we'd be better...
@gajus I'm curious what os your use case for `getHeaders`? Right now it's used internally to generate headers for each field, curious how it could be used outside of the...
When you pipe out of or submit FormData instance it contains that headers. Sounds like you're using separate pieces of FormData not the "product" itself. Unless I missed something.
I'm talking about FormData (this lib), trying better understand how it's being used. So we have current use casesin mind when thinking/talking about API changes. Maybe code example would help.
I see. Yes, it's me who confused myself :) getHeaders is used on submit, not on per field payload generation. :) And I see the use case. Looks like it's...
@takenspc Thanks for you interest. Do you mind to elaborate on the reason for this change?
How do you run it? Can you provide code example? Thank you.
You can supply your own `Content-Disposition` via `options.headers` – https://github.com/form-data/form-data/blob/master/lib/form_data.js#L181-L191