Camel behaviour change

[DavidS-ovm]

Hi,

this PR is to show the behaviour change of ToCamel/ToLowerCamel as of 0.3.0. The testcase in 262f4c7 passes for 0.2.0 but fails with 0.3.0.

[DavidS-ovm]

I'm not sure which way is "more correct", so I'm just leaving this here for others to find and (for the more knowledgeable of you) to decide.

[skunkworker]

I ran into this issue upgrading from 0.2.0 to 0.3.0 where an already camelized string that had a custom acronym would suddenly become lowercased.

eg:

0.2.0

ToCamel("APIController") -> "APIController"

0.3.0

ToCamel("APIController") -> "ApiController"

[wagoodman]

I ran into the same problem. I can see arguments both ways for correctness. Maybe allow for a separate function for the old behavior or make this configuable?

[laknoll]

I ran into a similar issue. I’d argue that changing behaviour is bad, as it can have quite a few unintended side effects for other packages. How about adding a separate method for the ‘new’ behaviour instead?

[jazanne]

+1 on adding a separate method for the ‘new’ behavior

[keaising]

I ran into a same issue, I think it is a BREAK CHANGE, maybe a new function to implement the new hehavior is better.

[alelevinas]

+1 on this being a BREAKING CHANGE and should be in release notes