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

Path prefix for all REST operations #141

Closed
jeaf-anaptecs opened this issue Apr 18, 2024 · 0 comments · Fixed by #150
Closed

Path prefix for all REST operations #141

jeaf-anaptecs opened this issue Apr 18, 2024 · 0 comments · Fixed by #150
Assignees

Comments

@jeaf-anaptecs
Copy link
Contributor

jeaf-anaptecs commented Apr 18, 2024

Feature Description

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
@jeaf-anaptecs jeaf-anaptecs added the feature New feature label Apr 18, 2024
@jeaf-anaptecs jeaf-anaptecs self-assigned this Apr 18, 2024
@jeaf-anaptecs jeaf-anaptecs changed the title Push REST path on operation only Path prefix for all REST operations Apr 22, 2024
jeaf-anaptecs added a commit that referenced this issue Apr 26, 2024
@jeaf-anaptecs jeaf-anaptecs linked a pull request Apr 26, 2024 that will close this issue
jeaf-anaptecs added a commit that referenced this issue Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant