-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
[REST-compliance] Naming convention for APIs #1273
Comments
Below a summary of the changes I want to do:
Counter-proposals are more than welcome. All of them could also be renamed later on the same pattern. I'm starting a PR to do all theses changes at once. |
looks good ! |
It seems OK for me as well :) Already compliant in brokers part 👍 |
Hello, For me all is good! I have only one remark; it's normal that the urls related to spring doc keep the verb " init " ? /api/servers/spring-boot/api-documentations/springdoc/init |
We merged the PR as it was pretty impactful but don't hesitate to challenge naming, strategy, etc. This can be considered as a draft preceding many improvements :) |
Following #144
Try to have something like
<collection>/<id>/<collection>/<id>/.../<element>
(URL "leaf" can be either a collection, an id or an element):/api/servers/spring-boot/databases/mysql
is compliant/api/svelte/styled
is not compliant, could be renamed to something like/api/clients/svelte/style
/api/servers/spring-boot/mvc/web/springdoc/init-with-security-jwt
is not compliant, could be renamed to something like/api/servers/spring-boot/api-documentations/springdoc/security-systems/jwt
This is to have a self explaining API and ready to add new options for each "tool" (ie:
oauth2
security method instead ofjwt
).The text was updated successfully, but these errors were encountered: