-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error Handling Example #3
Labels
duplicate
This issue or pull request already exists
⭐️ enhancement
New feature or request
help wanted
Extra attention is needed
Comments
Just confirming before I close this, is this a similar issue as the second part of #4? |
marksalpeter
added
duplicate
This issue or pull request already exists
help wanted
Extra attention is needed
and removed
help wanted
Extra attention is needed
labels
Dec 1, 2021
Closed in favor of #4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
duplicate
This issue or pull request already exists
⭐️ enhancement
New feature or request
help wanted
Extra attention is needed
Is your feature request related to a problem? Please describe.
I'm trying to use this wonderful library in one of my project, but I'm not sure how to handle processor errors correctly.
At the moment if an errors occurs the processor.Cancel method is called, but how is it intended by the library to actually
handle these errors by the caller?
Describe the solution you'd like
There should be a simple way to return an error channel from the processor.
Describe alternatives you've considered
Alternatively we have to pass an error channel to all the processor we use in the pipeline and send an error to that channel in the process.Cancel method.
Additional context
At the moment I've created a special Result type to be used by all the processors. It has an Err and a Value fields.
But the code is very verbose:
Any help or advice is appreciated.
The text was updated successfully, but these errors were encountered: