Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected casing when using numbers #58

Open
Techassi opened this issue May 24, 2024 · 1 comment
Open

Unexpected casing when using numbers #58

Techassi opened this issue May 24, 2024 · 1 comment

Comments

@Techassi
Copy link

This seems very related to #18.

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?

@gdnathan
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants