Fix controller middleware not resolving (#199) #203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since version
9.35.0of the Laravel framework, a PR was merged that changed the way controller middleware were resolved which lead to action middleware not being resolved.A follow-up PR was implemented on
laravel/framework(laravel/framework#44590) to enable Laravel Actions to keep its current behaviour whilst making sure the new behaviour from 9.35.0 is not broken.The goal of this PR is to perform the final update on Laravel Actions which leverages the latest PR on the framework.
Note that this fix will only work once a new version of the framework is published (anything that comes after
9.35.1).Fix #199.