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

🐛 (#198): Add example, remove operationID #214

Merged

Conversation

d135-1r43
Copy link
Collaborator

If the operationID is set, and it collides, then the OpenAPI gets broken. That resulted in #198. So we should no longer set the operationID and use the Quarkus default.

@d135-1r43 d135-1r43 linked an issue Dec 23, 2024 that may be closed by this pull request
Copy link
Contributor

@3thr3n 3thr3n left a comment

Choose a reason for hiding this comment

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

Quarkus default is not to set any operationId.

We could prevent this by using the autogeneration of operationId
Autogeneration

If the operationID is set and it collides, then the OpenAPI gets broken. That resulted in #198.
@d135-1r43 d135-1r43 force-pushed the 198-update-organisationvalidate-endpoint-to-make-it-usable branch from 3433bed to a3b5e8f Compare December 23, 2024 19:56
Copy link

@d135-1r43 d135-1r43 merged commit 1be25d2 into main Dec 23, 2024
10 checks passed
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.

Update organisation/validate endpoint to make it usable
2 participants