Francesco M

> @FrancYescO certainly correct: we are planning to introduce the switch to JSON:API as a new breaking change and major version. Sure, my suggestion was to keep the breaking changes...

yep this is my actual workaround :) i was searching just if there was some cleaner way maybe can be implemented like putting `limit` value to 0/-1 (if allowed by...

FYI, the workaround of setting an high default/maxLimit will cause a very inefficient query generated in case of relations on the table (something like https://github.com/ppetzold/nestjs-paginate/issues/329) that is not happening using...

The limit (and DoS protection) should be up to the dafault/maxLimit (so if the maxlimit is i.e. 20 don't allow the 0-infinite limit). Count + find will cause the result...

1) yep the PR maybe should be fixed to avoid allowing 0 if we have a 20 as maxlimit 2) yep 3) is what i want, if asking for a...

enableLimitRemoval: true == maxLimit: 0

> Okay with that as well. But then no pagination would be possible on that endpoint. So always infinite resource requests. pagination will be enabled if runtime i'll set the...

sure i was not saying to set as defaultLimit/maxLimit to 0 (neither this is done in the PR), but just to use maxLimit: 0 as a know-what-you-are-doing flag. there are...

just got another needs (get the total count of filtered items avoiding to get all datas) and probably a little rework on this PR can help... - `limit = 0`...

maybe easier in this way: maxLimit: 0 = allowed only to **count** elements in the table maxLimit: -1 = allowed to do unpaginated query (actual behaviour as 0) `http://localhost:3000/cats?limit=0&search=i&filter.age=$gte:3` ```...