Inverse Case Converter
iNVERSE writes hELLO wORLD. Inverse case flips every letter: it is the fastest fix for a paragraph typed with caps lock on, where every letter is exactly backwards including the intentional capitals. Unlike lower-casing and re-capitalising, inversion restores hELLO wORLD to Hello World in one pass without losing the sentence structure.
Conversions
| Input | iNVERSE |
|---|---|
hello world example | HELLO WORLD EXAMPLE |
XMLHttpRequest | xmlhTTPrEQUEST |
user_first_name | USER_FIRST_NAME |
Total Order Count | tOTAL oRDER cOUNT |
XMLHttpRequest becomes xmlhTTPrEQUEST. Applying the transformation twice returns the original exactly, which none of the other conversions here manage.The Same Text in Other Cases
| Case | Result |
|---|---|
| camelCase | helloWorldExample |
| PascalCase | HelloWorldExample |
| snake_case | hello_world_example |
| SCREAMING_SNAKE_CASE | HELLO_WORLD_EXAMPLE |
| kebab-case | hello-world-example |
| Train-Case | Hello-World-Example |
Where iNVERSE Fits
Inverting case is a repair operation: it is the one-step fix for a paragraph typed with caps lock engaged, where every letter is exactly backwards including the intended capitals. Lower-casing and re-capitalising cannot recover the same result.
Converting in Code
``javascript
const inverse = (s) =>
[...s].map((c) => (c === c.toUpperCase() ? c.toLowerCase() : c.toUpperCase())).join('');
`
Characters without a case ā digits, punctuation, most CJK ā pass through unchanged, so the operation is only an involution for cased scripts. Characters whose upper and lower forms differ in length, such as Ć, break the round trip.
Converting at the API Boundary
The recurring friction is that JavaScript uses camelCase and Python, Ruby, Go and SQL use
snake_case. The fix is to convert in exactly one place ā the client that talks to the API ā
rather than letting both conventions into the same codebase.
`javascript
const toCamel = (s) => s.replace(/_([a-z])/g, (_, c) => c.toUpperCase());
const toSnake = (s) => s.replace(/[A-Z]/g, (c) => '_' + c.toLowerCase());
// Recursively, for a whole payload
const convertKeys = (value, fn) =>
Array.isArray(value)
? value.map((v) => convertKeys(v, fn))
: value && typeof value === 'object'
? Object.fromEntries(Object.entries(value).map(([k, v]) => [fn(k), convertKeys(v, fn)]))
: value;
`
Two things to watch: keys that are user data rather than field names must not be
converted, and the round trip is not always lossless ā userID ā user_id ā userId
changes the original.
Where Each Convention Is Mandatory
Not stylistic ā these will break if you deviate:
| Context | Requirement |
|---|---|
| Environment variables | Uppercase with underscores; POSIX reserves lowercase |
| Custom HTML elements | Must contain a hyphen |
| Python modules | Cannot contain hyphens; the import statement will not parse |
| SQL identifiers | Folded to one case unless quoted, so camelCase does not survive |
| React components | Must start uppercase, or JSX treats it as an HTML tag |
Renaming Safely
A find-and-replace across a codebase will hit strings, comments and unrelated identifiers.
Use your language server's rename symbol instead ā it understands scope. For a bulk rename
across files, restrict the pattern with word boundaries and review the diff before
committing:
`bash
grep -rn '\buserId\b' src/ # look first
``