You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It seems that since the release 1.x, we cannot generate the AmqpChannelBinding but only AmqpOperationBinding inside an AsyncApiOperation. This was temporarily resolved in release 1.2.0-beta but was not propagated to further releases.
Describe the solution you'd like
An extra decorator (receiving an array of AsyncApiChannelBindings) that could be set at the method level could help achieve this by allowing to link a channel name used in Operation with a channel binding. The solution in release 1.2.0-beta was good for me.
Describe alternatives you've considered
Without this we cannot use the package for our use-case so currently our only solution is to keep using release 1.2.0-beta but we have to upgrade eventually.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It seems that since the release 1.x, we cannot generate the AmqpChannelBinding but only AmqpOperationBinding inside an AsyncApiOperation. This was temporarily resolved in release 1.2.0-beta but was not propagated to further releases.
Describe the solution you'd like
An extra decorator (receiving an array of AsyncApiChannelBindings) that could be set at the method level could help achieve this by allowing to link a channel name used in Operation with a channel binding. The solution in release 1.2.0-beta was good for me.
Describe alternatives you've considered
Without this we cannot use the package for our use-case so currently our only solution is to keep using release 1.2.0-beta but we have to upgrade eventually.
The text was updated successfully, but these errors were encountered: