- Which cases are supported?
- camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, Train-Case, dot.case, path/case, and Title Case. All common naming conventions in software.
- How does it detect word boundaries?
- Three heuristics: existing separators (spaces, underscores, hyphens), lowercase-to-uppercase transitions (camelCase splits), and number boundaries. Works on arbitrary mixed input.
- What about acronyms like HTTPServer?
- Configurable. Default treats consecutive capitals as a single token (HTTPServer → http_server). Strict mode splits them (HTTPServer → h_t_t_p_server).
- Does it preserve numbers?
- Yes — numbers are treated as their own token. `user2name` becomes `user_2_name` in snake_case or `user2Name` in camelCase.