Automatically register middleware in "web" group #147
Merged
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.
This PR updates the service provider to register the Inertia middleware in the
webmiddleware group, instead of the global middleware stack.The primary motivation for this change is because the current session reflashing behaviour does not work right now, and that's because the middleware is run before the session is started. Moving it to the end of the
webmiddleware group fixes this.inertia-laravel/src/Middleware.php
Lines 20 to 22 in 0a9af99
Also, it feels odd to register the Inertia middleware globally, when it should really only run on the
webendpoints, and not, for example, on theapiendpoints.