generator-jhipster
generator-jhipster copied to clipboard
Rely on OpenAPI generation for Controllers
Overview of the feature request
OpenApi maven plugin generates a bit of code based on swagger definition, I propose to rely on Contract first approach in order to generate jhipster's controllers.
Motivation for or Use Case
- Less code to maintain on Jhipster side (already achieved on open api side, api.yml contract already generated by JH)
- Contract first makes project more compatible with technologies like 'APIM' and the rest
- [x] Checking this box is mandatory (this is just to show you read everything)
So basically making the current "api first sub gen" the default and jhipster creates its own api spec?
This issue is stale because it has been open for too long without any activity. Due to the moving nature of jhipster generated application, bugs can become invalid. If this issue still applies please comment otherwise it will be closed in 7 days
Yes, this is the idea: use well known generator for what they are good at (i.e. OpenAPIgen, Liquibase entity gen, Mapstruct processor, ...), and jhipster generator using it as a basis for its contribution