pedanticOnlyRules top-level constant
Pedantic tier rules - pedantic, highly opinionated rules. Rules most teams would find excessive. For greenfield projects.
Implementation
const Set<String> pedanticOnlyRules = <String>{
// flutter_map (flutter_map_rules.dart) - thin-guard best-practice, opt-in
'flutter_map_missing_error_tile_callback',
// youtube_player_flutter (youtube_player_flutter_rules.dart) - high-FP heuristic
'youtube_player_auto_fullscreen_without_portrait_guard',
// Local Auth (local_auth_rules.dart) - naming-heuristic, high FP
'local_auth_biometric_only_sensitive',
// File length (very strict thresholds - 200 lines for production, 400 for tests)
'prefer_small_length_files', // 200 line limit
'prefer_small_length_test_files', // 400 line limit for tests
// Architecture preferences (very opinionated)
'prefer_feature_folder_structure', // folder organization preference
'prefer_custom_single_child_layout', // CustomSingleChildLayout for positioning
// Micro-optimizations (diminishing returns)
'avoid_object_creation_in_hot_loops', // loop allocation pedantry
'prefer_specific_numeric_types', // int vs num pedantry
// Documentation pedantry
// 'format_comment_style' moved to stylisticRules (opinionated)
'prefer_providing_intl_description', // i18n descriptions
'prefer_providing_intl_examples', // i18n examples
// Very strict patterns
'avoid_returning_widgets', // no widget helper methods
'avoid_nullable_widget_methods', // no nullable widget returns
// Bool params: in pedantic only to avoid duplicate diagnostics with avoid_positional_boolean_parameters_with_fix (professional)
'prefer_named_bool_params',
// Test pedantry
'avoid_duplicate_test_assertions', // no repeated assertions
// Tier 1 quick wins — batch 3
'start_comments_with_space', // INFO - // comment needs space after slashes
// Tier 1 quick wins — batch 4 (stylistic)
'getters_in_member_list',
'initializers_ordering',
'document_enum',
'new_instance_cascade',
'named_parameters_ordering',
'use_compare_without_case',
// Private-member DartDoc pedantry — `///` on a `_`-prefixed member never
// renders (private members are excluded from generated docs), so this is
// opinionated cleanup rather than a correctness or bug-risk signal.
'no_internal_method_docs',
};