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

Generate separate server-side OpenAPI endpoints/interfaces #13269

Closed
3 tasks
jdpgrailsdev opened this issue May 27, 2022 · 0 comments
Closed
3 tasks

Generate separate server-side OpenAPI endpoints/interfaces #13269

jdpgrailsdev opened this issue May 27, 2022 · 0 comments

Comments

@jdpgrailsdev
Copy link
Contributor

jdpgrailsdev commented May 27, 2022

Tell us about the problem you're trying to solve

Currently, the endpoints generated via OpenAPI are all in one class/interface. This prevents the ability to component-ize the implementation of the endpoints and prevents good practices, such as separation of concerns.

Describe the solution you’d like

The OpenAPI generation should be modified to set the useTags configuration option to true:

    configOptions = [
            dateLibrary  : "java8",
            generatePom  : "false",
            interfaceOnly: "true",
            useTags: "true"
    ]

for the server API generation. Note that the generator will still generate the single API, so this should not require any changes to the implementation.

Acceptance Criteria

  • Separate interfaces are generated for each "domain" in the server API
  • No modification required for existing implementation
  • All tests pass/API continues to function as expected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant