JEAF Generator uses UML models to generate code for Spring, REST, OpenAPI, Java and others. Boost your software development efficiency and time-to-market. Bye bye handwritten boiler blade code.
Sometimes standard http methods for REST operations are not sufficent. Google recommends for such cases to work with resource:doSomething as convention e.g. /customers:prepare and /customers:confirm.
If you just define that path on level of service operation everything is fine. However if you want to avoid the duplication of the general resource name and add that on service level in Spring and OpenAPI it results in /customers/:prepare.
This is not a generator issue, but anyways not what we would like to have.
Describe the solution you'd like
Allow to define the general path prefix for a resource on service level e.g. /customers
If configured accordingly genertor should merge that prefix without separator on the operation together with the operation path :prepare. This should result as /customer:prepare
Feature Description
Sometimes standard http methods for REST operations are not sufficent. Google recommends for such cases to work with
resource:doSomethingas convention e.g./customers:prepareand/customers:confirm.If you just define that path on level of service operation everything is fine. However if you want to avoid the duplication of the general resource name and add that on service level in Spring and OpenAPI it results in
/customers/:prepare.This is not a generator issue, but anyways not what we would like to have.
Describe the solution you'd like
/customers:prepare. This should result as/customer:prepare