Skip to content
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

ProcessingChain, nextError function #18

Open
smart--petea opened this issue Sep 6, 2014 · 2 comments
Open

ProcessingChain, nextError function #18

smart--petea opened this issue Sep 6, 2014 · 2 comments

Comments

@smart--petea
Copy link
Contributor

in runChain function there are a filtering on handler.name if it is supplied.
If a error is catched, processingChain instance will switch to error chain.
But nextError method does not support filtering by name.
Maybe to add it?

@deleteman
Copy link
Owner

@smart--petea I don't see the need to have error handlers set to a particular sub-set of endpoints... can you provide a real world example where you would need this? Otherwise I'm happy with the current implementation.

@smart--petea
Copy link
Contributor Author

For now, I can't find any.
But I think there may be the situation when user want to process the error in dependence of endpoint which generate it. A simple case can be the situation when the error branch is formed from one general handler for custom logger, second handle only for endpoint1 and third handle only for endpoint2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants