fix(core): resolve :param retrieval in prefix in middleware #13886
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?
Issue Number: #13401, #9776
PR #11832 caused issue #9776 when a global prefix was set and the exclude parameter was configured. Therefore, I reverted PR #11832 and fixed the issue it addressed using an alternative approach.
I added test cases based on the minimal reproduction code provided in #13401. This PR also resolves the issue in #13401.
The recent issues with middleware execution not behaving as expected all originate from PR #10390, which was implemented to resolve issue #9776. However, it has become clear that the changes introduced in that PR had too broad an impact. Therefore, in this PR, I have adjusted the logic so that the changes from PR #10390 only apply in cases where the prefix path contains
:param
, thereby minimizing the effect on most users.What is the new behavior?
Does this PR introduce a breaking change?
Other information