// library

Flutter (Stack) rules

42 rules

Severity

Bucket

ActiveBucketFlutter (Stack)Clear all

Low
Do Not Use Block Comments for Documentation
Use `///` for documentation instead of block comments to improve tooling support and ensure better formatting in generated docs.
docs-adrsstack-flutter+1
Low
DO title extensions using UpperCamelCase
Ensure that extensions use UpperCamelCase naming conventions (e.g., `MyExtension`). Avoid other casing styles that could reduce readability.
stack-flutterstyle-conventions
Low
DO title import prefixes using lowercase_with_underscores
Check that import prefixes use lowercase_with_underscores (e.g., `my_library`), following Dart's style guide.
stack-flutterstyle-conventions
Low
DO title other identifiers using lowerCamelCase
Ensure that identifiers such as variables and method titles are written in lowerCamelCase (e.g., `myVariable`). Avoid using other naming conventions.
stack-flutterstyle-conventions
Low
DO type annotate fields and top-level variables if the type isn't obvious
Check that fields and top-level variables are type-annotated explicitly when the type is not obvious from the context. This avoids ambiguity.
readability-refactorstack-flutter+1
Low
DON'T explicitly title libraries
Ensure that libraries are not explicitly titled. Dart provides automatic library titles, so avoid redundant naming of libraries in the code.
duplication-complexitystack-flutter+1
Low
DON'T make the parameter to == nullable
Ensure that parameters to `==` are non-nullable. Avoid using nullable parameters as they can introduce unexpected behavior and null reference errors.
error-handlingstack-flutter+1
Low
Extract complex conditional logic to separate methods
Move long/branchy UI decisions into named predicates or mappers to keep build methods simple.
readability-refactorstack-flutter
Low
Extract duplicated widget logic to reusable methods
Factor identical widget trees or builders into private helpers or dedicated widgets.
duplication-complexityreadability-refactor+1
Low
Extract magic numbers to named constants
Replace raw numeric/string literals used for dimensions, durations, and thresholds with named constants.
maintainabilityreadability-refactor+2
Low
Handle StateError from firstWhere operations
Always provide `orElse` to firstWhere (or use a safe helper) when the match may not exist.
error-handlingstack-flutter
Low
PREFER a noun phrase for a non-boolean property or variable
Ensure that non-boolean properties or variables are titled with noun phrases (e.g., `userDetails`, not `getUserDetails`). This improves readability.
readability-refactorstack-flutter+1
Low
PREFER using _, __, etc. for unused callback parameters
Check for functions with unused parameters and ensure they are titled with `_` or `__` to indicate they are intentionally unused.
maintainabilityreadability-refactor+1
Low
Refactor duplicated dialog action logic
Centralize repeated dialog creation/action handlers into a helper to ensure consistent UX and error handling.
duplication-complexityerror-handling+2
Low
Remove redundant null-assertion operators
Avoid `!` when nullability is already proven or a safer alternative (`??`, early return) exists.
readability-refactorstack-flutter+1
Low
Use `///` Doc Comments for Members and Types
Use `///` instead of regular comments to properly document Dart classes, methods, and properties for automatic documentation generation.
docs-adrsstack-flutter+1
Low
Use `const` Instead of `static final` Where Possible
Replace `static final` with `const` where applicable to enable compile-time evaluation and optimize performance.
performance-efficiencystack-flutter+1
Low
Use localized strings instead of hardcoded text
Read UI strings from a localization source (e.g., AppLocalizations, arb) rather than hardcoding.
internationalization-i18nstack-flutter

Do Not Use Block Comments for Documentation

DO title extensions using UpperCamelCase

DO title import prefixes using lowercase_with_underscores

DO title other identifiers using lowerCamelCase

DO type annotate fields and top-level variables if the type isn't obvious

DON'T explicitly title libraries

DON'T make the parameter to == nullable

Extract complex conditional logic to separate methods

Extract duplicated widget logic to reusable methods

Extract magic numbers to named constants

Handle StateError from firstWhere operations

PREFER a noun phrase for a non-boolean property or variable

PREFER using _, __, etc. for unused callback parameters

Refactor duplicated dialog action logic

Remove redundant null-assertion operators

Use `///` Doc Comments for Members and Types

Use `const` Instead of `static final` Where Possible

Use localized strings instead of hardcoded text

Do Not Use Block Comments for Documentation

DO title extensions using UpperCamelCase

DO title import prefixes using lowercase_with_underscores

DO title other identifiers using lowerCamelCase

DO type annotate fields and top-level variables if the type isn't obvious

DON'T explicitly title libraries

DON'T make the parameter to == nullable

Extract complex conditional logic to separate methods

Extract duplicated widget logic to reusable methods

Extract magic numbers to named constants

Handle StateError from firstWhere operations

PREFER a noun phrase for a non-boolean property or variable

PREFER using _, __, etc. for unused callback parameters

Refactor duplicated dialog action logic

Remove redundant null-assertion operators

Use `///` Doc Comments for Members and Types

Use `const` Instead of `static final` Where Possible

Use localized strings instead of hardcoded text