You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When converting v1alpha1 to PascalCase, I expect the result to be V1Alpha1, however, V1alpha1 is produced. Adding an API mentioned in #18 (comment) could solve this issue by setting number_starts_word: true.
Is there currently any way to produce the expected outcome, or should this be accepted as intended behaviour?
The text was updated successfully, but these errors were encountered:
I'd like to add something.
Whatever the final decision is (to keep lowercase after number or not), I think the option to have the other option would be beneficial.
In case of cross language project, it can cause incompatibilities if one camel_case library use one strategy, and an other one use a different one, as seen in this issue
This seems very related to #18.
When converting
v1alpha1
to PascalCase, I expect the result to beV1Alpha1
, however,V1alpha1
is produced. Adding an API mentioned in #18 (comment) could solve this issue by settingnumber_starts_word: true
.Is there currently any way to produce the expected outcome, or should this be accepted as intended behaviour?
The text was updated successfully, but these errors were encountered: