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.

Sign up for GitHub

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

Jump to bottom

Bug Report: The OpenApi @Schema "name" property does not rename annotated class attribute/FISH-5778 #5429

Open
silvafabio opened this issue Sep 29, 2021 · 1 comment
Open

Bug Report: The OpenApi @Schema "name" property does not rename annotated class attribute/FISH-5778 #5429

silvafabio opened this issue Sep 29, 2021 · 1 comment
Assignees
@shub8968
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect

Comments

@silvafabio
Copy link

Description

When annotate an class attribute with @Schema(name = "newName") the attribute appear twice at the generated documentation, one with old name and one with the new name.

Expected Outcome

Only one occurence with the new name.

Current Outcome

Appear twice at the generated documentation, one with old name and one with the new name.

Steps to reproduce

Reproduce project attached.

payara-openapi-schema-name-error.zip

Run the project and call /openapi endpoint.

Environment

  • Distribution: 5.2021.7 Server Full Profile
  • JDK Version: zulu8.40.0.25-ca-jdk8.0.222-linux_x64
  • Operating System: Linux
@silvafabio silvafabio added Status: Open Issue has been triaged by the front-line engineers and is being worked on verification Type: Bug Label issue as a bug defect labels Sep 29, 2021
@shub8968 shub8968 self-assigned this Sep 30, 2021
@shub8968 shub8968 changed the title Bug Report: The OpenApi @Schema "name" property does not rename annotated class attribute Bug Report: The OpenApi @Schema "name" property does not rename annotated class attribute/FISH-5778 Oct 3, 2021
@shub8968 shub8968 added Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev and removed Status: Open Issue has been triaged by the front-line engineers and is being worked on verification labels Oct 3, 2021
@shub8968
Copy link
Contributor

shub8968 commented Oct 3, 2021

Hi @silvafabio, I am able to reproduce this issue. I have raised an internal issue with JIRA FISH-5778. Thanks. It may take a while to fix the issue. You are free to submit a PR to fix this issue if you feel confident to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shub8968 shub8968

Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@silvafabio @shub8968