[
  # Template compilation warnings - these are false positives from Phoenix LiveView template compilation
  # These warnings are due to template compilation and cannot be easily fixed without breaking UI logic
  ~r/lib\/aprsme_web\/live\/info_live\/show\.html\.heex/,
  ~r/lib\/aprsme_web\/live\/weather_live\/callsign_view\.html\.heex/,

  # False positive: The nil pattern is handled in the case statement above, dialyzer doesn't track this correctly
  {"lib/aprsme/packets.ex"},

  # False positive: Aprs.parse/1 does return {:ok, _} but dialyzer can't see the vendored library types
  {"lib/aprsme/is/is.ex"},

  # False positive: PacketUtils.get_weather_field can return various types including nil
  {"lib/aprsme_web/live/weather_live/callsign_view.ex"},

  # False positive: Ecto.Multi uses opaque internal types — call_without_opaque on Ecto.Multi.update/3
  # is a known dialyzer limitation with Ecto.Multi's opaque MapSet-backed names field
  {"lib/aprsme/accounts.ex", :call_without_opaque},

  # False positive: Gettext uses Expo.PluralForms opaque types internally; Gettext.Plural.plural/2
  # is called with a tuple that satisfies the runtime contract but violates the opaque type spec
  {"lib/aprsme_web/gettext.ex", :call_without_opaque},

  # False positive: MapSet.t() is opaque; the @spec is correct at the semantic level but dialyzer
  # sees through the opaque wrapper to the underlying map representation
  {"lib/aprsme/packets/prepared_queries.ex", :contract_with_opaque},

  # False positive: to_float/1 has a %Decimal{} clause for completeness but dialyzer infers
  # nil | number() from the call sites in mobile_channel — the clause is defensive dead code
  {"lib/aprsme_web/channels/mobile_channel.ex"},

  # False positive: symbol_table_id is typed as binary() by dialyzer at this call site; the nil
  # guard in the && expression can't match binary(), but the function can receive nil in practice
  {"lib/aprsme_web/live/info_live/show.ex", :guard_fail},

  # Mix.Task PLT limitations: Mix.Task behaviour types and Mix.shell/0 are not available
  # in the dialyzer PLT; also the aprs library's return type is inferred incorrectly from
  # the compiled beam without full type specs
  {"lib/mix/tasks/aprs.parse_file.ex"},

  # Mix.Task.Compiler PLT limitations: same root cause — Mix.* functions and the
  # Mix.Task.Compiler.Diagnostic struct aren't in the dialyzer PLT.
  {"lib/mix/tasks/compile/unused.ex"},

  # Mix.Project PLT limitations: Mix.Project.compile_path/0 and
  # Mix.Project.config/0 are not present in the dialyzer PLT, and Code.ensure_loaded
  # is treated as having an unmatched return when used for side-effect.
  {"lib/mix_unused/analyzer.ex"},

  # Phoenix LiveViewTest false positive: render_hook/3 and render/1 internally access
  # view.ref which only exists on View, but the type specs say Element | View.
  # Dialyzer can't narrow the live/3 return type from Element | View to just View.
  {"test/aprsme_web/live/map_live/movement_test.ex"},

  # Compiler type-checking false positives: these test files use patterns that trigger
  # type warnings from the Elixir compiler. All are pre-existing and benign.
  {"test/aprsme/packets_mic_e_test.exs"},
  {"test/aprsme/packets_test.exs"},
  {"test/aprsme/is_test.exs"}
]
