Converting naming cases in one pass
Paste names one per line and camelCase, PascalCase, snake_case, kebab-case and CONSTANT_CASE all appear in a single table. You can copy any one column in full, which suits bulk work such as turning a list of database columns into code field names.
Everything hinges on how a name is split into words. Underscores, hyphens, dots and spaces break it, and a run-together name breaks where a lowercase letter meets an uppercase one. Acronyms are the hard part: whether parseHTTPResponse should become parseHttpResponse or stay as it is has no single agreed answer and varies by language and linter, so both choices are offered. Digit boundaries work the same way, attached or split.
Characters outside letters and digits become a chunk of their own and take no case change. Names in scripts without letter case cannot be re-cased, and the output says how many were skipped that way. Reserved-word checks and per-language identifier validation are not performed.
Frequently Asked Questions
Into parse, HTTP and Response. With acronyms treated as words you get parseHttpResponse, and with capitals kept you get parseHTTPResponse. snake_case gives parse_http_response either way.
They split identically into user and ID, but the camelCase output differs: keeping acronym capitals gives userID, while treating them as words gives userId.
Their characters are kept as they are, because a script without letter case cannot take a naming convention. The output note reports how many names were skipped.