constant-naming-convention

The standard naming convention for TypeScript constants uses concise ALL_UPPERCASE identifiers for fixed compile-time values, while preserving lowercase runtime keys inside constant objects for routes, statuses, and lookups to maintain code readability.

To format enum-like constants and lookup maps in Angular, use short uppercase identifiers for the constant itself and lowercase keys for the runtime object properties, ensuring consistent casing for maintainable code style.

Object keys inside a TypeScript constant should be lowercase at runtime, even when the constant identifier itself is uppercase, to preserve consistent casing for configuration values, lookup maps, and route statuses.

Yes, this constant naming approach applies to Angular dependency injection tokens and feature flags, requiring short descriptive uppercase names for these shared constants to ensure repository-local frontend maintainability.

Using uppercase for compile-time constants and lowercase for runtime object keys in TypeScript distinguishes fixed values from dynamic properties, reducing inconsistent identifiers and making Angular feature flags and configuration objects easier to read.