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.

Sign up for GitHub

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

Jump to bottom

Document general naming guidance for Casing #1349

Open
noahdietz opened this issue May 9, 2024 · 1 comment
Open

Document general naming guidance for Casing #1349

noahdietz opened this issue May 9, 2024 · 1 comment
Labels
aip: requested New AIP needed for a particular topic

Comments

@noahdietz
Copy link
Collaborator

Internally the question is asked a lot - how should we case acronyms in non-Field proto element names. We've basically always tried to follow "Google Java" style of PascalCase where acronyms are treated as english words e.g. API -> Api, gRPC -> Grpc, UI -> Ui.

This should likely be a general AIP on naming for non-Field elements (since Fields have go/aip/140).
@noahdietz noahdietz added the aip: requested New AIP needed for a particular topic label May 9, 2024
@noahdietz
Copy link
Collaborator Author

Internal link: http://yaqs/7173108306494357504

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aip: requested New AIP needed for a particular topic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@noahdietz