analysis_options.yaml

# This file configures the analyzer, which statically analyzes Dart code to
# check for errors, warnings, and lints.
#
# The issues identified by the analyzer are surfaced in the UI of Dart-enabled
# IDEs (https://dart.dev/tools#ides-and-editors). The analyzer can also be
# invoked from the command line by running `flutter analyze`.

# The following line activates a set of recommended lints for Flutter apps,
# packages, and plugins designed to encourage good coding practices.
include: package:flutter_lints/flutter.yaml

analyzer:
  exclude:
    - lib/generated/**
    - lib/firebase_options.dart
    - "**/*.g.dart"
    - "**/*.freezed.dart"
    - "**/*.pb.dart"
    - "**/*.pbenum.dart"
    - "**/*.pbjson.dart"
    - "**/*.pbserver.dart"
    - meshcore-open/**
    - MeshCore-Firmware/**
    - meshtastic-ios/**
    - mesh-observer/**
    - sigil-api/**
    - tool/**
  errors:
    # Suppress deprecation warnings from generated protobuf files
    # These are maintained upstream by the Meshtastic protobufs project
    # and we regenerate them from the official proto definitions.
    # The deprecation warnings are for backwards compatibility and cannot
    # be fixed without breaking changes to the Meshtastic protocol.
    deprecated_member_use: ignore
    deprecated_member_use_from_same_package: ignore

linter:
  # The lint rules applied to this project can be customized in the
  # section below to disable rules from the `package:flutter_lints/flutter.yaml`
  # included above or to enable additional rules. A list of all available lints
  # and their documentation is published at https://dart.dev/lints.
  #
  # Instead of disabling a lint rule for the entire project in the
  # section below, it can also be suppressed for a single line of code
  # or a specific dart file by using the `// ignore: name_of_lint` and
  # `// ignore_for_file: name_of_lint` syntax on the line or in the file
  # producing the lint.
  rules:
    # Disabled: use_null_aware_elements lint incorrectly suggests ?key: value
    # for map entries with nullable values. The ?key syntax only works when
    # the KEY is nullable, not the value. The existing if (v != null) pattern
    # is the correct approach for conditionally including map entries with
    # nullable values.
    use_null_aware_elements: false
    # avoid_print: false  # Uncomment to disable the `avoid_print` rule
    # prefer_single_quotes: true  # Uncomment to enable the `prefer_single_quotes` rule

# Additional information about this file can be found at
# https://dart.dev/guides/language/analysis-options