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
feat(types): use retry-as-promised types for retry options to match documentation #15400
Conversation
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.
There are a few small differences between the current state and the types package but I do think we should prefer the types package over our own type. Thanks for this PR!
Yes there are. My hope is that this is not a breaking change for anyone. I'm happy to open a new PR against |
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.
🚀🎉
Note that @mickhansen is going to refactor |
402ff75
to
44c043d
Compare
Waiting on mickhansen/retry-as-promised#37 |
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.
If tests are green, we're good to go :)
@ephys will this get a backport release to v6? |
@esetnik we should be able to, can you open a new PR towards the v6 branch? |
Pull Request Checklist
Description Of Change
I have corrected the types in the underlying
retry-as-promised
library so they can now be re-exported by sequelize to get the proper type forretry
.See DefinitelyTyped/DefinitelyTyped#63267 for details.