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
{{ message }}
This repository has been archived by the owner on Aug 24, 2019. It is now read-only.
I was reading the class that implements the validation logic to run the rate limit.
While reading the class method below:
private class func shouldExecute(name name: String, limit: NSTimeInterval) -> Bool
I've notice the lookup date is updated regardless if 'should' is true or false.
I would expect the last executed date to be updated when the limit has passed. That way, subsequent request could refer to the original date instead of the last checked date.
Sorry for not making a pull request.
The text was updated successfully, but these errors were encountered:
I was reading the class that implements the validation logic to run the rate limit.
While reading the class method below:
private class func shouldExecute(name name: String, limit: NSTimeInterval) -> Bool
I've notice the lookup date is updated regardless if 'should' is true or false.
I would expect the last executed date to be updated when the limit has passed. That way, subsequent request could refer to the original date instead of the last checked date.
Sorry for not making a pull request.
The text was updated successfully, but these errors were encountered: