Skip to content
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.

Missing rationale behind API suffix #573

Open
azolotko opened this issue Feb 15, 2021 · 0 comments
Open

Missing rationale behind API suffix #573

azolotko opened this issue Feb 15, 2021 · 0 comments

Comments

@azolotko
Copy link

azolotko commented Feb 15, 2021 •
edited
Loading

Uber Protobuf Style Guide V2 says:

Services should always be suffixed with API. For example, TripAPI or UserAPI. This is for consistency.

"For consistency" argument is understandable, but it doesn't unfortunately explain why API suffix was chosen. This rule contradicts Google's Style Guide and it would be nice to understand why this divergence was introduced. It could've just been just "Service" suffix, right?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@azolotko