Skip to content

Potential issues with defined lints sets #737

@mit-mit

Description

@mit-mit

I compared the lints listed in the yaml files here against my internal notes, and I'm seeing the following potential issues:

Core lints

Missing from this repo

  • always_declare_return_types
  • unawaited_futures

Recommended lints

  • avoid_empty_else
  • avoid_private_typedef_functions
  • avoid_relative_lib_imports
  • avoid_shadowing_type_parameters
  • avoid_types_as_parameter_names
  • await_only_futures
  • camel_case_extensions
  • camel_case_types
  • curly_braces_in_flow_control_structures
  • empty_catches
  • file_names
  • hash_and_equals
  • iterable_contains_unrelated_type
  • list_remove_unrelated_type
  • no_duplicate_case_values
  • non_constant_identifier_names
  • omit_local_variable_types
  • package_prefixed_library_names
  • prefer_generic_function_type_aliases
  • prefer_is_empty
  • prefer_is_not_empty
  • prefer_iterable_whereType
  • prefer_mixin
  • prefer_typing_uninitialized_variables
  • provide_deprecation_message
  • unnecessary_overrides
  • unrelated_type_equality_checks
  • use_rethrow_when_possible
  • valid_regexps
  • void_checks

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions