Fix issue #78: Separate OpenAPI specs for multiple middleware instances #79
Conversation
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
henry232323
force-pushed
the
fix-issue-78
branch
from
9f71f08 to
a0d0d37
Compare
…re instances - Store owned routes directly on middleware instance using Set - Filter routes to exclude those owned by other OpenAPI middlewares - Ensures each middleware only includes its own routes while preserving sub-router compatibility
henry232323
force-pushed
the
fix-issue-78
branch
from
a0d0d37 to
466298c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If this is by design, feel free to close this PR. This PR fixes #78 and separates out the OpenAPI specs if they are registered to different middleware.