Styling Dart Code

Contents

• Naming Conventions
• Ordering Directives
• Formatting Rules
• Workflows

Naming Conventions

Apply the following naming conventions strictly to maintain consistency across the Dart ecosystem.

• Types: Name classes, enum types, typedefs, extensions, and type parameters using UpperCamelCase.
• Variables & Members: Name class members, top-level definitions, variables, parameters, and named parameters using lowerCamelCase.
• Constants: Prefer lowerCamelCase for constant variables, including enum values.
  • Conditional: If editing existing code that uses SCREAMING_CAPS or working with generated code (e.g., protobufs), maintain consistency with the existing style.
• Files & Directories: Name packages, directories, and source files using lowercase_with_underscores.
• Import Prefixes: Name import prefixes using lowercase_with_underscores.
• Acronyms: Capitalize acronyms and abbreviations longer than two letters like regular words (e.g., Http, Uri). Keep two-letter acronyms fully capitalized (e.g., ID, UI). If an abbreviation begins a lowerCamelCase identifier, make it entirely lowercase (e.g., httpConnection).
• Privacy: Use a leading underscore _ for members and top-level declarations to indicate library privacy. Do not use leading underscores for local variables, parameters, local functions, or library prefixes.