-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update for v5 #370
update for v5 #370
Conversation
branches: 96 | ||
functions: 100 | ||
lines: 100 | ||
statements: 98 | ||
|
||
disable-coverage: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't it better to impose a fixed limit, so that we're aware when the code coverage drop?
Maybe we can open an issue to increase code coverage if possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can open an issue to increase code coverage if possible.
Yes
Isn't it better to impose a fixed limit, so that we're aware when the code coverage drop?
I'm not aware if that exists in tap@20, happy to add it back if so
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not aware if that exists in tap@20, happy to add it back if so
Yep, they broke a few things.
Maybe it's better to fix coverage in an independent PR, will take a look tomorrow
* Updating for v5 (#338) * ci: add node 21 to test matrix and remove node 14 and 16 * package.json update for v5 * merge main to next (#348) * Update README.md to reflect #307 (#342) * Redis should work with ban (#336) * Redis should work with ban * fix ttl * simplify * format * remove warning * move property * add test * fix test * fix test * fix test * still fix the same test * make it non-breaking * make it non-breaking * make it non-breaking * make it non-breaking * perf: add ban back * Bumped v8.1.0 Signed-off-by: Matteo Collina <[email protected]> * Bumped v9.0.0 Signed-off-by: Matteo Collina <[email protected]> * Fix in-memory cache bug when there is only one entry (#345) * Bumped v9.0.1 --------- Signed-off-by: Matteo Collina <[email protected]> Co-authored-by: Trevor Lund <[email protected]> Co-authored-by: Matteo Collina <[email protected]> Co-authored-by: Igor Savin <[email protected]> * Revert "merge main to next (#348)" This reverts commit 5446122. * revert workflow update as its causing issues (#350) * revert: handle ban in store (#347) * remove ban handling from store * don't use negation * add undef * don't pass ban to promis * fix accidental explicit checks * fix accidental line change * inline ban * Workflow v4 (#354) * refactor: make RedisStore default key a default parameter (#356) * refactor redis parameters and throw if no instance was provided * revert error * Add function support for timeWindow (#357) * feat: dynamic time window support * fix: proper usage of timeWindowString --------- Co-authored-by: lukas <[email protected]> * update docs (#360) * fix: remove unnecessary parameter timeWindow (#363) * refactor: consistent option handling (#365) * small refactor in option handling * simplify * simplify * perf: pregenerate `timeWindow` string when possible and use `noop` as default function (#364) * pregenerate timeWindowString if possible * simplify * simplify * noop * simplify * simple-example * rename * update for v5 (#370) * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update for v5 * update fastify deps --------- Signed-off-by: Matteo Collina <[email protected]> Co-authored-by: Eliphaz Bouye <[email protected]> Co-authored-by: Gürgün Dayıoğlu <[email protected]> Co-authored-by: Trevor Lund <[email protected]> Co-authored-by: Matteo Collina <[email protected]> Co-authored-by: Igor Savin <[email protected]> Co-authored-by: lukas <[email protected]> Co-authored-by: lukas <[email protected]> Co-authored-by: Gürgün Dayıoğlu <[email protected]>
t.teardown
is problematic, since the tests are sync, we can just clear them up in the end