-
Notifications
You must be signed in to change notification settings - Fork 36
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
refactor: Extract pieces to make them more testable #66
Conversation
13c54c2
to
d79197d
Compare
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 like it and I think it's the way to go. I guess we need to improve the interface / trait documentation over time. Let's not get this PR too big. If you're happy with the names and docs, I think you can already merge it and start a new one with a new series of patches.
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 like, I like a lot 😄
Some minor naming niggles
3e6c35c
to
ade4aa3
Compare
ade4aa3
to
553460a
Compare
Connects to #49 .
This set of commits attempts to refactor some of the retry code to allow for mocking and unit testing, as well as some code reuse. I highly recommend reviewing commit-by-commit.
Names of the extracted methods are Friday-afternoon quality and should be changed to whatever everyone likes, assuming that you like the direction of these refactorings.
There's absolutely more that can be done here, but this is as far as Jake and I got today. Do you like this? 🥺 👉🏻 👈🏻