Skip to content
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

feat(core): add info.summary to additionalProperties for 3.1 specs #19723

Merged
merged 1 commit into from
Oct 2, 2024

Conversation

joscha
Copy link
Contributor

@joscha joscha commented Sep 30, 2024

This adds the content of the info.summary property to the additionalProperties in case it is non-empty.

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package 
    ./bin/generate-samples.sh ./bin/configs/*.yaml
    ./bin/utils/export_docs_generators.sh
    
    (For Windows users, please run the script in Git BASH)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@@ -343,6 +344,12 @@ private void configureOpenAPIInfo() {
config.additionalProperties().put("unescapedAppDescription", info.getDescription());
}

if (this.openAPI.getSpecVersion().equals(SpecVersion.V31) && !StringUtils.isEmpty(info.getSummary())) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The swagger lib yields null for info.getSummary() in non-3.1 specs, so this guard could potentially be removed, however as we don't provide a fallback like we do for the description property, I find the spec version guard more obvious for any future readers of this code.

@wing328
Copy link
Member

wing328 commented Oct 2, 2024

thanks for the PR. lgtm

fyi @OpenAPITools/generator-core-team

@wing328 wing328 merged commit c5060a2 into OpenAPITools:master Oct 2, 2024
15 checks passed
@joscha joscha deleted the joscha/app-summary branch October 2, 2024 09:08
@joscha
Copy link
Contributor Author

joscha commented Oct 2, 2024

thanks for the PR. lgtm

thank you! Could I get your 👀 on this one please #19696 by any chance?

@wing328 wing328 added this to the 7.9.0 milestone Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants