chore: Refactor SwaggerGen to support multiple values with the same path #145
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
Signed-off-by: dwertent <[email protected]>
EnriqueL8
reviewed
Aug 16, 2024
Signed-off-by: dwertent <[email protected]>
EnriqueL8
reviewed
Aug 16, 2024
| @@ -116,7 +116,7 @@ func (sg *SwaggerGen) getPathItem(doc *openapi3.T, path string) *openapi3.PathIt | |||
| if doc.Paths == nil { | |||
| doc.Paths = &openapi3.Paths{} | |||
| } | |||
| pi := doc.Paths.Find(path) | |||
| pi := doc.Paths.Value(path) | |||
There was a problem hiding this comment.
Just being careful with this, as it would affect all the swagger documents generated from now on
Is there a scenario where normalising does make sense? I tried to find the history in the kin-openapi repo and it seems that it was there from the original commit
There was a problem hiding this comment.
Ok, we can wait for a response here.
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.
This PR offers an alternative solution to the issue addressed in this PR. Rather than modifying the API, we've adjusted the behavior of the Swagger generation to ensure the value is no longer ignored.