Addition of new middleware, RoutesBuilderMiddleware #32
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
Westie
changed the title
|
Note to @TartanLeGrand - please don't merge this yet as I need to ensure that this is still working, but the unit tests I made a year or so ago still work as expected. |
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.
I'm working on a project that involves autodocumenting API endpoints, as well as manually documenting endpoints that are not procedurally generated.
The purpose of this PR is to introduce a new middleware - RouteInformationMiddleware - that allows a developer to have a bit more control over the RouteInformation object.
In addition, as part of this PR, I would also like to propose that we can now optionally pass the RouteInformation instance to any operation builder.
Tests and doc changes supplied.
Related to vyuldashev#103