Introduce content type into generated JSON types#1078
Merged
deepmap-marcinr merged 2 commits intomasterfrom Jun 2, 2023
Merged
Introduce content type into generated JSON types#1078deepmap-marcinr merged 2 commits intomasterfrom
deepmap-marcinr merged 2 commits intomasterfrom
Conversation
adrianpk
pushed a commit
to foorester/oapi-codegen
that referenced
this pull request
Jan 16, 2024
* Introduce content type into generated JSON types As noted in oapi-codegen#1051, we have cases where multiple uses of JSON types leads to a clash in generated type names. This is a slight breaking change for folks' generated code, but ensures that conflicts do not happen, and that we are more predictable with generated type names. Closes oapi-codegen#1051. * Add gorilla/mux to the README
adrianpk
added a commit
to foorester/oapi-codegen
that referenced
this pull request
May 31, 2024
* Introduce content type into generated JSON types As noted in oapi-codegen#1051, we have cases where multiple uses of JSON types leads to a clash in generated type names. This is a slight breaking change for folks' generated code, but ensures that conflicts do not happen, and that we are more predictable with generated type names. Closes oapi-codegen#1051. * Add gorilla/mux to the README
danicc097
pushed a commit
to danicc097/oapi-codegen
that referenced
this pull request
Aug 31, 2024
* Introduce content type into generated JSON types As noted in oapi-codegen#1051, we have cases where multiple uses of JSON types leads to a clash in generated type names. This is a slight breaking change for folks' generated code, but ensures that conflicts do not happen, and that we are more predictable with generated type names. Closes oapi-codegen#1051. * Add gorilla/mux to the README
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
2 participants
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.
As noted in #1051, we have cases where multiple uses of JSON types leads
to a clash in generated type names.
This is a slight breaking change for folks' generated code, but ensures
that conflicts do not happen, and that we are more predictable with
generated type names.
Closes #1051.