go-naming

Enforce consistent Go naming by applying MixedCaps for identifiers, avoiding underscores, and following initialism rules. This aligns packages, functions, variables, and constants with Google and Uber style guidelines.

Google and Uber Go style guidelines require MixedCaps for identifiers without underscores. They provide specific rules for initialisms, receiver names, package names, and test names to maximize code clarity and maintainability.

Name Go receiver variables consistently using short, clear abbreviations of the type name. Follow style guidelines to ensure receiver names remain uniform across methods, improving readability during code reviews.

No, you should not use underscores in Go variable and constant names. Idiomatic Go style mandates MixedCaps or camelCase for multi-word identifiers instead of snake_case to maintain codebase consistency.

Handle initialisms like ID or HTTP in Go identifiers by keeping them consistently capitalized. Style guidelines dictate that initialisms should remain uppercase for acronyms to ensure visual consistency across the codebase.

Apply Go style guide rules during code reviews, onboarding, and refactoring. Enforcing naming conventions at these stages maintains idiomatic Go style and prevents inconsistent identifier naming from harming codebase readability.