Makes an arrayLimit configurable

[seeden]

Please, can you add arrayLimit (qs library) as optional parameter like a parameterLimit?
For this I created request month ago. ljharb/qs#18

[dougwilson]

Hi! I'm not sure how I was supposed to know that your issue over in qs meant you wanted an option over here :)

In any case, the default for this library is an arrayLimit of 100. I do not plan to add the ability to configure anything qs-specific through this library as this time. It's the reason the option is extended: true and not parser: 'qs'--to keep the parsing library abstracted.

If you really want me to, please describe to me a really good reason you need an arrayLimit different from 100 and also why you cannot send JSON instead of a urlencoded body.

[seeden]

Maybe you do not understand me. You guys are doing a great job. I am using body-parser with expressjs for parsing of post requests with extended = true. Few versions before was this limit hard coded to 20 in a QS library. Because your library is in the middle of expressjs and qs I would like to have a option to set this optional parameter. Is it possible?

[dougwilson]

Well, it is not possible at this time, no, but I'm just trying to understand why you would need to make it configurable. The main reason I don't really want to is because this library is trying to hide the fact that extended: true is even using qs. As far as the user is concerned, it could be using foobuzz to parse the query string.

I added parameterLimit because the option works for both extended: true and extended: false. arrayLimit is really an implementation detail of just the qs module and it doesn't even apply to the querystring module.

I did bump up the default from 20 to 100 recently. Do you still need a larger limit? If so, you really need to be using JSON bodies and not urlencoded bodies. The extended urlencoded bodies are there purely for HTML <form> entries. You surely do not have a HTML <form> with over 100 <input> elements, do you?

[seeden]

Thanks for explanation. I will use bodyParser.json() with (application/json) instead of bodyParser.urlencoded.