fix(microservices): fix rabbitmq no-assert not being applied correctly #13285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
noAssert
flag is a state property on theServerRMQ
andClientRMQ
classes but it's not being used.Instead, the
queueOptions.noAssert
is used to determine if theassertQueue
should be called or not (can be seen here for server and here for client)This means that the
noAssert
flag is not used, at all.What is the new behavior?
This PR makes sure to use the
noAssert
property of the class, instead of reading it from thequeueOptions
The current workaround (without this PR) is to pass in the
noAssert
flag in thequeueOptions
like this:In order to remain completely backward compatible, I've introduced a fallback on
queueOptions.noAssert
, so ifnoAssert
is not provided, it falls back toqueueOptions.noAssert
before using the default value.Please let me know if you don't agree with this fallback mechanism, I'd be more than happy to change the PR accordingly.
Does this PR introduce a breaking change?
Other information