Merge several middleware classes #11489
Labels
status: accepted
This issue has been accepted for implementation
type: housekeeping
Changes to the application which do not directly impact the end user
Milestone
Proposed Changes
Merge the following middleware classes into one:
Justification
Each of these middleware classes is responsible for a fairly minor yet crucial operation, and it doesn't really make sense that we would need to toggle them individually.
Note that I'm excluding
RemoteUserMiddleware
from this list, as it holds a considerable amount of custom logic, and we want to ensure it's always processed before the boilerplate stuff.The text was updated successfully, but these errors were encountered: