When select multiple I think the return always has to be an array

[rafagomes]

When I select multiple, in your module I read in your code that when you select one item the return is the file and if the length > 1 return an array, this forces the user to always verify.

It's simplier if the user select multiple, return always an array.

I did this, if you agree I can do the Pull Request.

[KevinPoole]

This is an issue that I have also ran into and would like to see the prescribed fix implemented.

[tunnckoCore]

Yea, I think the same too. #341, #354, #386 and #400

[kornelski]

Requirements for this feature:

• 100% backwards compatible. Leave the existing field exactly as it is. This package has been stable for a very long time. Let's avoid splitting userbase by bumping semver-major. New feature can be added to a new field.

• The user shouldn't need to sniff types to use it properly. Specifically, it can't be sometimes a file and sometimes an array. The new field that supports multiple files should always be an array with 1 or more items. This way it won't be possible to break applications that hardcode read of .name by sending two files under name.

[GrosSacASac]

I propose: Make the multiple always return arrays for both fields and files.

It does not need a new flag and is backwards compatible as application using multiples: true should already have an if else for arrays or objects.

I can make a new PR. Also #315 (review)

[charmander]

@GrosSacASac It’s not backwards-compatible: multiples: true previously didn’t affect fields.

[tunnckoCore]

I think we are going to release v2 directly, so it's okay.

What about if we separate it to multipleFields and multipleFiles? And probably preserve multiples too for affecting both.

[GrosSacASac]

npm i node-formidable/formidable#3.x