majiayu000 Dart Best Practices
Priority: P1 (OPERATIONAL)
Best practices for writing clean, maintainable Dart code.
- Scoping:
- No global variables.
- Private globals (if required) must start with
_.
- Immutability: Use
const>final>var. - Config: Use
--dart-definefor secrets. Never hardcode API keys. - Naming: Follow effective-dart (PascalCase classes, camelCase members).
- Strings: Prefer single quotes; use double quotes only for interpolation needs.
- Trailing Commas: Always use trailing commas for multi-line literals/params.
- Expression Bodies: Prefer
=>for single-expression functions/getters. - Collections:
- Use
.map,.where,.fold,.anyover manual loops when clarity improves. - Type empty collections (
<String>[],<String, User>{}) to avoiddynamic. - Use collection
if/forand spread operators for composable lists/maps.
- Use
- Async: Always
awaitfutures unless intentionally fire-and-forget.
import 'models/user.dart'; // Good
import 'package:app/models/user.dart'; // Avoid local absolute