Allow use of middleware result builder in Router
#512
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.
Middleware are stored as
Middleware<Request, Response, Context>
instead ofRouterMiddleware
. Once middleware result builder is moved to separate package this allows for outside libraries to create Middleware that can be used by Hummingbird without knowing aboutRouterMiddleware
(an HB type).RouterMiddleware
is just a helper protocol to avoid having to setInput
andOutput
in hummingbird specific middleware.The work above has allowed me to move the middleware stack to Hummingbird so users can take advantage of it in the Hummingbird standard router. eg