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

Consider saying that custom methods **should** use GET or POST. #128

Open
rofrankel opened this issue Mar 14, 2024 · 0 comments
Open

Consider saying that custom methods **should** use GET or POST. #128

rofrankel opened this issue Mar 14, 2024 · 0 comments

Comments

@rofrankel
Copy link
Collaborator

          Let's go back to the Google guidance here.
  • The HTTP method must be GET or POST:
    • GET must be used for methods retrieving data or resource state.
    • POST must be used if the method has side effects or mutates resources or data.
  • The HTTP URI must use a : character followed by the custom verb (:archive in the above example), and the verb in the URI must match the verb in the name of the RPC.
    • If word separation is required, camelCase must be used.

Originally posted by @mkistler in #103 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant