Roman

Results 72 comments of Roman

@dmurvihill Hey, interesting approach. It could be created as a new package based on `rate-limiter-flexible`. After that we could add it to docs.

@dmurvihill Could you write a usage example? Probably, for `RateLimiterRedis` as it is the most popular limiter. I'll add it to the docs.

@hffmnn This matters only if you pay for storage. In case of billions of items stored in DynamoDB it may be expensive. Is it your concern?

@hffmnn rate-limiter-flexible logic doesn't rely on the existence of items. Instead, it checks `expire` value and compares it with the current time. Maybe you found a bug? Could you share...

@hffmnn Thanks! It looks like `get` method is buggy. As a workaround `msBeforeNext` could be checked. It should return correct 0 or -1 value when an item has expired.

Hi @avifenesh Could you clarify? Would you like to rename `RateLimiterMemcache` to `RateLimiterMemcached` (with `d` at the end) ?

Could we support both names and deprecate the one with typo?

Or it can be extended from the renamed class like: ```js class RateLimiterMemcache extends RateLimiterMemcached { constructor(options) { super(options); console.warn( 'RateLimiterMemcache is deprecated and will be removed in a future...

@sevauni Hey, this PR looks almost ready. I put a couple of comments.