2026-06-08 · 4 min read
- naming
- api
Different layers of a stack expect different casing. JavaScript prefers camelCase; PostgreSQL columns often use snake_case; URL paths and CSS classes use kebab-case. Automated conversion prevents manual rename errors during integrations.
Convention by context
- camelCase — JavaScript objects, Java fields
- snake_case — Python, Ruby, SQL columns
- kebab-case — HTML attributes, URLs, CSS classes
- PascalCase — React components, C# types
API boundary tip
Document the canonical JSON casing in OpenAPI. Convert at the client SDK boundary instead of letting every service guess.