Capitalizes the first letter of camelCase names, turning userProfile into UserProfile. PascalCase is the convention for classes, TypeScript types and interfaces, React components and C# members, so this conversion shows up whenever a value-level name has to become a type-level one.
Unlike the other conversions from camelCase, nothing is split here: the existing word boundaries are kept and only the first character changes. That also means acronyms survive intact.
String.Result.interface userProfile { id: number }
interface orderSummary { total: number }
type paymentMethod = "card" | "bank";interface UserProfile { id: number }
interface OrderSummary { total: number }
type PaymentMethod = "card" | "bank";The interface and type names are capitalized, while id and total are single lowercase words and are not treated as camelCase, so the field names stay as they are.
paymentMethod → PaymentMethod.userID → UserID, homeURL → HomeURL.userId2 → UserId2.Generated or quickly written code sometimes has interface userProfile. Converting the declarations brings them in line with the usual TypeScript lint rule for type names.
From a route or state key such as orderSummary, get the OrderSummary component name, or turn service variable names into class names when extracting them into their own files.
user, id) are not camelCase and are left alone.userID keep ID here but become user_id on the snake_case page?Going from camelCase to PascalCase only changes the first character, so the inner capitals are kept exactly as written. Targets that use separators have to lowercase every word, so there ID turns into id.
No. Title Case capitalizes separate words with spaces between them. PascalCase keeps words joined; use the string case converter for titles.