Daniel comments

Results 210 comments of


                                            Daniel

feat: add option to change the default value of the `Parse.Query.limit()` constraint

Could you check the failing tests?

feat: add option to change the default value of the `Parse.Query.limit()` constraint

@vzukanov thanks for your work on this PR. We are so close, just a few minor changes and tests to fix. I can take on this PR if you would...

feat: add option to change the default value of the `Parse.Query.limit()` constraint

How so?

feat: add option to change the default value of the `Parse.Query.limit()` constraint

No worries - I think we’re good to merge now. @vzukanov, we just needed to fix some of the failing tests (`npm test`). You can run individual tests by changing...

feat: add option to change the default value of the `Parse.Query.limit()` constraint

Sorry @mtrezza - I am on mobile and I just realised that this throws if `maxLimit` is less than or equal to 0, so `!maxLimit` is preferred over `maxLimit ==...

feat: add option to change the default value of the `Parse.Query.limit()` constraint

Reverted my previous change as it failed the tests - this is good to merge

feat: add rate limiter

> Is it possible to specify different values for different routes Yes, the option is an array and can specify specific routes if required. ```js rateLimitOptions: [ { path: '/functions/*',...

feat: add rate limiter

This also moves session lookup into its own middleware so that the rate limiter is performed _before_ any database ops are ran

feat: add rate limiter

Thank you for the thorough review @mtrezza :)

I've just read that `express-rate-limit` doesn't support clusters either. Perhaps [rate limit flexible](https://www.npmjs.com/package/rate-limiter-flexible) is a better option? Also supports using mongo/postgres as a backing store, and cluster mode. [Also has...