Open
Conversation
Allow to define a Router as target which allows nesting of several indipendent router. This makes routers reuseable
Member
|
Almost 11 years late 🐼 This is indeed a wanted feature, but lots of things happen since then. For example, when we initially created Rest, the PSRs for HTTP didn't existed yet. The fact that now they do, and middlewares exist, potentially changes how we might approach this. I'll investigate this use case further, and report back here. For now, I've implemented basic downstream HTTP middlewares as per PSR-15, which is not enough, but sets a direction for delegation inside the core that we might decide to reuse later. |
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.
Allow to define a Router as target which allows nesting of
several indipendent router. This makes routers reuseable.
See #119.