-
Notifications
You must be signed in to change notification settings - Fork 17
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
method naming conventions #169
Comments
Path to API Enlightenment - REST over JSON-RPCBased on Richardson Maturity Model description of the different layers of REST APIs. But applied with OpenRPC in mind:
|
Another resource reinforcing naming with |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@shanejonas is there something still to be done here? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
would be great to follow the naming conventions outlined here |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem? Please describe.
As a developer, i'd like clear naming conventions to remove unnecessary variation.
I've also outlined my thoughts around how this naming and it being a foundational layer to get a RESTful style interface with JSON-RPC here.
gRPC's naming conventions:
https://cloud.google.com/apis/design/naming_convention#method_names
VerbNoun
The text was updated successfully, but these errors were encountered: