This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
Move middleware into subnamespace #54
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
weierophinney
added a commit
to weierophinney/zend-expressive-router
that referenced
this pull request
Mar 1, 2018
This was referenced Mar 1, 2018
Per the [migration roadmap](https://discourse.zendframework.com/t/roadmap-expressive-2-2/504), all middleware shipped by this component need to be in a subnamespace, as that's where they will be in version 3. This patch moves the route and dispatch middleware to the `Zend\Expressive\Router\Middleware` namespace, and then creates extensions under the original names that are immediately deprecated.
weierophinney
force-pushed
the
feature/middleware-namespace
branch
from
ca68fd7
to
194b2fe
Compare
weierophinney
added a commit
that referenced
this pull request
Mar 6, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Per the migration roadmap, all middleware shipped by this component need to be in a subnamespace, as that's where they will be in version 3.
This patch moves the route and dispatch middleware to the
Zend\Expressive\Router\Middlewarenamespace, and then creates extensions under the original names that are immediately deprecated.