We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In issues #553, #575 & #566, the exception policy for this client isn't clear and causes some user confusion.
The policy should be stated clearly. Either we don't allow exceptions in callbacks or we do allow them and then handle them in a very specific way.
Additionally we should consider allowing exceptions in callbacks with a well-defined behaviour to propagate those exceptions.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
🚀 Feature Request
In issues #553, #575 & #566, the exception policy for this client isn't clear and causes some user confusion.
The policy should be stated clearly. Either we don't allow exceptions in callbacks or we do allow them and then handle them in a very specific way.
Additionally we should consider allowing exceptions in callbacks with a well-defined behaviour to propagate those exceptions.
🔈 Motivation
🛰 Alternatives
📎 Additional context
The text was updated successfully, but these errors were encountered: