New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 750136 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Sync] EntryResponse field inconsistently named in sync.proto

Project Member Reported by s...@chromium.org, Jul 28 2017

Issue description

"EntryResponse" in sync.proto has an inlined definition and usage. While it's name conforms to typical message naming pattern, the field name ens up being "entryresponse" when it should be "entry_response". We should be able to fix this without breaking any compatability.
 

Comment 1 by s...@chromium.org, Jul 28 2017

Summary: [Sync] EntryResponse field inconsistently named in sync.proto (was: EntryResponse field inconsistently named in sync.proto)
Status: WontFix (was: Untriaged)
Group name is used for both class name and field name generation. It must start with capital letter. 

We can rename EntryResponse to Entry_Response which will change field name to entry_response, but that will change type name to Entry_Response which is used in multiple places (commit_util.h for example). 

We cannot switch from group to message without affecting wire format.

Resolving as won't fix as fixing it introduces different naming issue.

Sign in to add a comment