Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Encapsulate retry logic #101

Closed
jmgasper opened this issue Oct 2, 2018 · 0 comments
Closed

Encapsulate retry logic #101

jmgasper opened this issue Oct 2, 2018 · 0 comments

Comments

@jmgasper
Copy link
Collaborator

jmgasper commented Oct 2, 2018

The handleEventGracefully logic needs to be moved out of the IssueService and into it's own class. For instance, we want the same retry logic to apply to creating the Topcoder challenge for a copilot payment, but that would currently require redundant code, so we need to get the retry logic better encapsulated to make it more useful to all the individual services, both current and future.

jmgasper pushed a commit that referenced this issue Oct 23, 2018
* #105  (major requirement)
* #104
* #103 (major requirement)
* #101
* #94
* #92
* #91
* #85 (major requirement)
jmgasper pushed a commit that referenced this issue Oct 9, 2019
* #105  (major requirement)
* #104
* #103 (major requirement)
* #101
* #94
* #92
* #91
* #85 (major requirement)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant