Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Mar 4, 2022. It is now read-only.
This repository was archived by the owner on Mar 4, 2022. It is now read-only.

Missing rationale behind API suffix #573

Open
@azolotko

Description

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /