-
Notifications
You must be signed in to change notification settings - Fork 113
[#1369] Add @SuppressWarnings to generated client classes #1370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
File renamed without changes.
2 changes: 1 addition & 1 deletion
2
...ntegration-tests/jsonproperty-getter-and-setter/src/main/resources/application.properties
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| quarkus.openapi-generator.codegen.spec.jsonproperty_openapi_yaml.base-package=org.acme.jsonproperty.gettersetter | ||
| quarkus.openapi-generator.codegen.spec.jsonproperty_openapi_json.base-package=org.acme.jsonproperty.gettersetter |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I previously worked on the PR that added @JsonProperty to pojo setters but realized I made the file extension of a json file
yamlinstead. Kinda breaks one of the checkboxes for the PR ("Pull Request does not include fixes for issues other than the main ticket") so I can pop off this commit if you guys are strict about itThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this passed the integration tests then. I wonder if we are trying to parse to JSON first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually took a look at this last night because I was wondering the same thing. I had traced it down to here: https://github.com/swagger-api/swagger-parser/blob/ef2cf163dfdf19af5a5a8dc1ab6651dcfcd43924/modules/swagger-parser-v3/src/main/java/io/swagger/v3/parser/util/DeserializationUtils.java#L245
Looks like it just tries the json parser if the yaml is invalid
Not 100% sure that's actually the reason it still worked since I didn't bother step through with the debugger to verify that this is where it is parsing it, but it's my best guess.