[12.x] Unset global middleware deactivation when running withoutMiddleware with filled parameters #55478
+14
−0
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.
Currently when we run consecutive tests in the same test-case (eg: few calls to do E2E testing), there is a situation which make
withoutMiddleware
usage discussable.The second call to
withoutMiddleware()
will currently don't change nothing as the first call set the instancemiddleware.disable
totrue
.What is your opinion on the fact to unset it if we call
withoutMiddleware
with given parameters ?This PR should not impact current usages.