Wrong timeToExpire unit

[AntunVukicevic]

timeToExpire value returned from the increment function is in milliseconds instead of seconds. Because of that NestJs ThrottlerGuard sets the wrong Retry-After header in the HTTP response when the throttling limit is hit.

From the quick debug session, it looks like calling the PTTL Redis command returns milliseconds that are not converted to seconds afterwards.

[slavafomin]

I can confirm this issue. The content of the Retry-After header is incorrect. It should contain seconds, while in practice it contains milliseconds. I think we should convert millis to seconds here right before we return the result to the guard.

[kkoomen]

Hi. Thanks a lot for noticing this, unfortunately this became a problem during the big rewrite last time. The tests did check for a number, but not a specific number. I've modified tests to make sure the secs are beings checked to make sure this won't happen again in the future.

I've just released this immediately under v0.3.2 on NPM.