Allow custom middleware to be registered#1892
Merged
taylorotwell merged 1 commit into13.xfrom Feb 22, 2026
Merged
Conversation
timacdonald
commented
Feb 22, 2026
Comment on lines
+18
to
+19
| 'middleware' => [], | ||
|
|
Member
Author
There was a problem hiding this comment.
I'm sure this could use some Taylor comment love.
This file contains hidden or 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.
Like other packages, such as Fortify, Nova, and Horizon, this adds the ability to add custom middleware, via config, to the routes passport registers.
The motivation behind this feature is to allow us to intercept any passport routes and enforce certain rules. The main one being that the
client_idmust be a UUID.Right now, when someone hits our application with
client_id=123, a query exception is thrown as the database is expecting a UUID. For most databases, it probably just 404s, but for certain databases, they error out when the wrong type is used for the query.This would allow us to create a similar pattern we use for our routes, where we 404 before we even hit the database, e.g.,
The middleware will allow us to handle query parameters (the current problem) as well as route parameters.