Open badeadan opened 5 years ago
This is actually an issue that camelcase
should mean that the first letter is lowercase. Pascalcase (function does not exist) is where the first letter is uppercase.
https://docs.microsoft.com/en-us/archive/blogs/brada/history-around-pascal-casing-and-camel-casing
https://www.theserverside.com/answer/Pascal-case-vs-camel-case-Whats-the-difference https://khalilstemmler.com/blogs/camel-case-snake-case-pascal-case/ https://betterprogramming.pub/string-case-styles-camel-pascal-snake-and-kebab-case-981407998841 https://stackoverflow.com/questions/41768733/camel-case-and-pascal-case-mistake
So the problem is that sprig has a bug. It would be nice if a new version was published that fixed this.
"snakecase" documentation refers to camelCase to suggest the transformation of someString to _somestring but then "camelcase" documentation refers to CamelCase suggesting _somestring is converted to SomeString
I tested this with a helm chart and:
is rendered as:
where the 1st character is transformed by "camelcase" to upper.
Wikipedia definition states:
Fixing this is breaking compatibility with older versions so I suggest an update to the documentation page to point to huandu/xstrings definition of Camel case: