| name | Dart Best Practices |
|---|---|
| description | General purity standards for Dart development. |
| metadata | {"labels": ["dart", "clean-code"], "triggers": {"files": ["**/*.dart"], "keywords": ["import", "final", "const", "var", "global"]}} |
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).
import 'models/user.dart'; // Good
import 'package:app/models/user.dart'; // Avoid local absolute