You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We love your published library and very likely to use it.
One idea to improve is to return not just a simple boolean but a rich object of type {isOverLimit:boolean, limitingRule:RequestLimitRule} or similar.
Exact type is not critical, it's just the idea of letting the user (be it internal or external) - which limit was reached.
So currently - the user would just get false when she's limited.
After - she'd know what exactly blocked her access.
WDYT?
p.s
I know it's a major refactor to internal logic + interface.. but it can be done in a non-breaking mode
The text was updated successfully, but these errors were encountered:
Craig, we are making extensive usage of your library to control/limit some protocols. Works like a charm so far (combined with Redis). Returning which limit rule was reached is definitively an important tuning feature. Many thanks for your great job.
We love your published library and very likely to use it.
One idea to improve is to return not just a simple
boolean
but a rich object of type{isOverLimit:boolean, limitingRule:RequestLimitRule}
or similar.Exact type is not critical, it's just the idea of letting the user (be it internal or external) - which limit was reached.
So currently - the user would just get
false
when she's limited.After - she'd know what exactly blocked her access.
WDYT?
p.s
I know it's a major refactor to internal logic + interface.. but it can be done in a non-breaking mode
The text was updated successfully, but these errors were encountered: