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(connection): call specific error response codes (DEV-3339) #832
refactor(connection): call specific error response codes (DEV-3339) #832
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.
What I am most unhappy with, is that the error handling that lives in the connection object is too specific for such a generic class.
In my opinion what could work is that we do
- a network action without
- the first types of responses are generic as they can happen with any input, for these responses we have the loop automatically
- the second types of error handling are specific depending on when the function is used (xmlupload, create, etc.)
- There we work out the problem
- communicate that
- if it is an error that we want to retry, we enter a function that executes the loop (for simplicity's sake no matter what type of response it gets, it will retry the set amount of times.
- if we don't want to retry we continue
Do you think something like that is feasible?
…hub.com/dasch-swiss/dsp-tools into wip/dev-3339-connection-live-error-codehnadling
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.
LGTM
@jnussbaum I was not able to request a review from you, probably because you opened the PR, but I would be glad for your input. |
@nora: LGTM |
No description provided.