Ensure member names in error strings are referred to with correct case to ensure they aren't loc'ed #960

Closed
DamianEdwards opened this Issue Nov 13, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@DamianEdwards
Member

DamianEdwards commented Nov 13, 2012

Resources that refer to actual properties should be capitalized appropriately so that we know whether or not to lock the strings, eg
0; Error_ProtocolErrorMissingConnectionId Text Protocol error: Missing connection id. !EOSum!Protocol error: Missing connection id. 表©鷗字㌍!
Does connection id refer to a parameter or property name (connectionId or ConnectionId)?

@ghost ghost assigned halter73 Nov 14, 2012

@halter73

This comment has been minimized.

Show comment Hide comment
@halter73

halter73 Dec 4, 2012

Member

Fixed by 32dee3c

Member

halter73 commented Dec 4, 2012

Fixed by 32dee3c

@rustd

This comment has been minimized.

Show comment Hide comment
@rustd

rustd Dec 4, 2012

verified

rustd commented Dec 4, 2012

verified

@rustd rustd closed this Dec 4, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment