camelCase, snake_case, kebab-case: Who Uses Which
One name in five styles, where each is the norm, and where they meet in real projects.
By the TurantTools Dev team · Updated October 27, 2026 · 2 min read
Every ecosystem has a naming habit, and mixing them makes code harder to read and search. Here's "user account id" in each style and where it's used.
| Where | Style | Result |
|---|---|---|
| JavaScript / TypeScript variables | camel | userAccountId |
| Classes and React components | pascal | UserAccountId |
| Python, Ruby, SQL columns | snake | user_account_id |
| CSS classes, URLs, file names | kebab | user-account-id |
| Environment variables, constants | constant | USER_ACCOUNT_ID |
Where they meet
- APIs between a Python back end and a JS front end often convert snake_case JSON to camelCase at the boundary; pick one place to do it.
- Acronyms:
userIdoruserID? Choose one rule and let a linter enforce it. - Database columns in snake_case avoid quoting in PostgreSQL, which folds unquoted names to lowercase.