Product
Hot Chocolate
Is your feature request related to a problem?
The HotChocolate.Subscriptions.RabbitMQ Package depends on the RabbitMQ.Client Package Version 6.4.0 which is 3 years old as of now.
When trying to combine RabbitMQ Subscription Management of HotChocolate on the Same Server that implements an Event-Driven Architecture using MassTransit for example, also using RabbitMQ as its message broker you will run into Version-Conflicts because of their dependent Package.
But the kicker is, you won't even realize this since the HotChocolate.Subscriptions.RabbitMQ Package, from my understanding, uses reflection to call Functions on the IModel Interface of the RabbitMq.Client Package, which no longer exists in its current versions.
The solution you'd like
The dependency to RabbitMQ.Client upgraded to it's current version (7.1.2) and maybe try to use it without reflection so you would get Compile-Time Errors when working in combination with other Versions of RabbitMQ.Client from other packages.
Product
Hot Chocolate
Is your feature request related to a problem?
The
HotChocolate.Subscriptions.RabbitMQPackage depends on the RabbitMQ.Client Package Version 6.4.0 which is 3 years old as of now.When trying to combine RabbitMQ Subscription Management of HotChocolate on the Same Server that implements an Event-Driven Architecture using MassTransit for example, also using RabbitMQ as its message broker you will run into Version-Conflicts because of their dependent Package.
But the kicker is, you won't even realize this since the
HotChocolate.Subscriptions.RabbitMQPackage, from my understanding, uses reflection to call Functions on theIModelInterface of theRabbitMq.ClientPackage, which no longer exists in its current versions.The solution you'd like
The dependency to
RabbitMQ.Clientupgraded to it's current version (7.1.2) and maybe try to use it without reflection so you would get Compile-Time Errors when working in combination with other Versions of RabbitMQ.Client from other packages.