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
Thanks for this project! It's been really helpful on my project to map between a couple different systems that have different capitalization conventions.
Specifically, I've used pascalCase and camelCase, but for single words without spaces. (e.g., converting Foobar <-> foobar)
This works fine, but I wonder if it would make sense to have different named operations, that don't have space-inserting behavior. E.g.:
I recognize that there are so many specific combinations, that it could get out of hand quickly (and be difficult to name them all). Maybe there's another way to design the API? (composable functions/types?)
The text was updated successfully, but these errors were encountered:
Thanks for this project! It's been really helpful on my project to map between a couple different systems that have different capitalization conventions.
Specifically, I've used
pascalCase
andcamelCase
, but for single words without spaces. (e.g., convertingFoobar
<->foobar
)This works fine, but I wonder if it would make sense to have different named operations, that don't have space-inserting behavior. E.g.:
I recognize that there are so many specific combinations, that it could get out of hand quickly (and be difficult to name them all). Maybe there's another way to design the API? (composable functions/types?)
The text was updated successfully, but these errors were encountered: