Skip to content

Conversation

@eyalpost
Copy link
Contributor

@eyalpost eyalpost commented Dec 23, 2018

Added a few test cases that did not work well in the previous version
Should fix #1009 and #1130

…nName() implementation

Added a few test cases that did not work well in the previous version
@JustinBeckwith JustinBeckwith changed the title Fixed camelCase implementation to be compatible with Protobuf's ToJsonName fix: ensure camelCase implementation is compatible with Protobuf's ToJsonName Apr 19, 2019
@nicolasnoble
Copy link
Member

This most likely would cause breaking changes in dependents...

@murgatroid99
Copy link
Contributor

To expand on that, if any existing user has a field name that matches one of the patterns of a name that transforms differently as a result of this change, their code that references those fields will break after this change.

@eyalpost
Copy link
Contributor Author

eyalpost commented May 26, 2019

@murgatroid99 @nicolasnoble
Well, currently this creates a mess when the same proto file is exposed by different technologies and the same client tries to use them.
I think you should leave this open and target a fix for the next major version when a breaking change is ok

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Camel case conversion bug with numbers in field names

3 participants