-
Notifications
You must be signed in to change notification settings - Fork 134
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
feat(AIP-191): compare service casing to packaging #984
feat(AIP-191): compare service casing to packaging #984
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this basically ensures that we treat all definitions in a case sensitive manner, correct?
Yep. It is common (per Client libs team) to have mismatched proto packaging annotation values and service name as the former is just a string and is easy to mess up, whereas the service name itself is much more of a "first class" element. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noahdietz:packaging-issues
A first step towards protecting services and packing annotations from having mismatched names e.g.
service Foobar
andoption c_sharp_namespace = "Google.FooBar.V1"
whereFoobar
andFooBar
do not match in casing.@jskeet