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
Currently, when --preserve-case is used to translate a CamelCase replacements to additional lowercase and uppercase replacements, it inserts underscores in between the word segments. This is cool, but on some occasions it would be useful to additionally do the replacement without the added underscores.
Agree in principle. Just still thinking what the flags should be, so that there isn't a proliferation of random flags for every type of case convention. For example, the cleanest solution may be a pregen step that takes one pattern file and "case generalizes" it to another pattern file (and handles CAPS, dromedaryCamel, BactrianCamel, under_score, dash-style, and runtogether formats) that can be inspected/edited before use.
Currently, when
--preserve-case
is used to translate a CamelCase replacements to additional lowercase and uppercase replacements, it inserts underscores in between the word segments. This is cool, but on some occasions it would be useful to additionally do the replacement without the added underscores.For example, the current behaviour is like this:
It would be awesome if it could be extended to do this:
Perhaps this could be opt-in.
The text was updated successfully, but these errors were encountered: