Dmitry Kirilyuk
Dmitry Kirilyuk
Pagination is fetching and counting. If we set `limit: 0` we disable fetching. It's very cool
5.0.0 and 5.0.3 are working. They are identical. `master` is broken for a long time, I'll fix it later when move code to es6 and node6 (https://github.com/edwardhotchkiss/mongoose-paginate/pull/73)
This is actually not so rare situation :+1: I need also both http and https
Redirect from http to https also would be ok
@sokra Looks like this is not rare situation :smiley:
By default `qs` is considering the following `ids=43750&ids=70936&ids=94691` as an array. That's why I think that `qs` should apply `arrayLimit` also to array notation without brackets. This is where I...
With `a[0]=1&a[99999999999999999999999]=2` it makes sense, yes 👍
@ljharb I've submitted the PR. I intentionally specified that the problem is only with iteration over the array (and this iteration happens in `qs` itself). There are no other issues.
From documentation: > When creating arrays with specific indices, qs will compact a sparse array to only the existing values preserving their order: ```js var noSparse = qs.parse('a[1]=b&a[15]=c'); assert.deepEqual(noSparse, {...
Honestly I think `arrayLimit` can be removed in near feature. All arrays handled in `qs` can be wrapped in `Object.values`, `Object.entries` where needed. These methods do not iterate over arrays,...