c('e2e') about camelcase

[dazip]

The new behavior is consistent with lodash.camelcase

• https://www.npmjs.com/package/lodash.camelcase

The old behavior is consistent with case.camel

• https://www.npmjs.com/package/case

[sindresorhus]

Not really sure which one is the most appropriate. I'm leaning towards e2E.

// @DanielSeehausen @eladb @Qix-

[Qix-]

Yep agreed.

[eladb]

golly... so many edge cases. Is this a unique case because after the number there’s only a single character?

[dazip]

Same would apply for any number of characters after the numeric. Please consider whether it would be appropriate to revert to 5.2.0 behavior in 5.x.x and bump to 6.0.0 for 5.3.0/5.3.1 changes.

[sindresorhus]

Alright, let's keep the current behavior.

[sindresorhus]

Please consider whether it would be appropriate to revert to 5.2.0 behavior in 5.x.x

That would be a breaking change for people depending on the new behavior, so not going to happen. Better to just leave it like this.

[DanielSeehausen]

sorry for late reply -- just seeing this! (let me fix my notification settings now)
e2E would also be my vote, as numbers should act as delimiters in camel casing!
seems to follow the original intent of the code as well, and know lodash has been mentioned as a north star here.