Naming suggestions

[mernst]

Thanks for string-inflection! As a new user, I have some suggestions about naming, which you might want to consider.

"snake case" is the more common name for what string-inflection calls "underscore". It would be helpful to users to change the name or add an alias.

It is inconsistent that string-inflection uses "camelcase" (one word) but "pascal-case" and "kebab-case" (two words).

The naming "single" confused me. It means "symbol at point". I suggest renaming and/or clarifying the documentation. The documentation of string-inflection--single-or-region is currently not very informative: "Perform INFLECT-FUNC depending on if in region or single."

In the documentation of string-inflection-get-current-word and elsewhere, "the cursor" is more idiomatically called "point".

[akicho8]

Thank you for your feedback.

When I first created this package, I designed it mainly for my own use with the mindset of "as long as it works." Also, since I’m not a native English speaker, there ended up being many unnatural parts in naming and such, which has continued until now.

"underscore" → "snake_case"
You’re absolutely right. When people hear "underscore," they usually think of the character _ itself, so it’s confusing as a style name.

Naming consistency (camelcase vs pascal-case / kebab-case)
I’d like to unify these as well. However, I was a bit hesitant when ChatGPT pointed out that changing upcase to up-case feels unnatural.

Meaning and naming of "single"
Since the current implementation targets symbols, I’m considering renaming single-or-region to symbol-or-region as it would be more appropriate.

"cursor" → "point"
I agree with you that in the context of Emacs, "point" is a more accurate term than "cursor."

Maintaining backward compatibility while adding aliases would complicate the code, so I’m thinking of reorganizing and renaming everything at once instead.

[mernst]

Regarding "up-case", I agree that you would leave that as one word "upcase", rather than two.

[akicho8]

As I thought, up case does feel a bit off. While I found that upper case is also a commonly used term, in Ruby, we write it as upcase, and since I'm used to that, I decided to stick with upcase.