-
Notifications
You must be signed in to change notification settings - Fork 33
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 update per Design Guideline #96
Path update per Design Guideline #96
Comments
I've observed that some APIs within Camara incorporate the term "get" as a verb in their endpoints. Therefore, it is essential to ensure consistency in the naming conventions for actions associated with all APIs whether to use "get" or "retrieve" |
Agreed with this request and that we should change our path as We can follow guideline (probably we're supposed to do this way) but looking to device-locatin API family I saw following path: So not sure if we move to alignement with the rule ( |
@akoshunyadi: I tried to resubmit (twice) but it doesn't appear in the list of PRs. Let me know please if you don't see the PRs. |
@gmuratk I can see the PR, but it is a PR against your forked main and not the official main, that's why it doesn't appear at the PRs above |
Thanks @akoshunyadi ! I think this time I reopened it in the right place successfully. |
Problem description
Following paths must be verbs per design guideline:
/connectivity
/roaming
From Design Guideline:
Expected behavior
"/connectivity" may be changed to "/retrieve-connectivity-status"
and
"/roaming" may be changed to "/retrieve-roaming-status"
Alternative solution
Additional context
The text was updated successfully, but these errors were encountered: