-
Notifications
You must be signed in to change notification settings - Fork 595
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
Only throw RabbitMQ.Client
-specific exceptions.
#1439
Comments
Thank you @paulomorgado for taking the time to open this issue with great details. Relevant comments - 169a6d1#r134239817 |
RabbitMQ.Client
-specific exceptions.
Exceptions thrown by this library could include the associated connection and channel as exception data to allow library users to take appropriate action. Thoughts? @paulomorgado |
All the information that can be provided is always helpful. Exceptions have a But this is not very discoverable and people usually choose to add the data as custome exception properties. If you are creating scenario specific exceptions, you can create properties for that. But I wouldn't mind having them as data. |
Closing! See this comment. |
Describe the bug
From Using Standard Exception Types:
RabbitMQ code should return RabbitMQ exceptions. If there was another exception causing the one being thrown, it should be added as an
InnerException
.Reproduction steps
ServiceBase.Notify
is throwingSystem.Exception
at https://github.com/rabbitmq/rabbitmq-dotnet-client/blob/main/projects/RabbitMQ.Client/client/impl/SessionBase.cs#L128Expected behavior
a RabbitMQ-specific exception is thrown.
Additional context
No response
The text was updated successfully, but these errors were encountered: