DCM

Features

Analyze

Lint Rules

Metrics

Widgets Analysis

Assets Analysis

Other features

Fix

Maintain

Configure

Integrate

Description

1class _MyState extends State<MyWidget> {
2  @override
3  Widget build(BuildContext context) {
4    setState(() {
5      myState = "Hello, Flutter!";
6    });
7
8    return Text(myState);
9  }
10}

Use 375+ unique configurable rules to find bugs, memory leaks, and consistency and readability issues.

Learn More

For Dart, Flutter and Packages

Enable rules for Dart, Flutter, and packages such as "Provider", "Bloc", "Riverpod", "Equatable" and other.

Quick Fixes

Use IDE quick fixes or "dcm fix" to automatically fix highlighted fixable issues.

Familiar Configuration

Use familiar "analysis_options.yaml" file to configure DCM to serve you the best.

Customers Pricing Docs Changelog Blog Watch Demo

match-lib-folder-structure

added in: 1.11.0

warning

Pro+

Warns when the file path in the test folder does not match the implementation file path in the lib folder.

Keeping the same folder structure for your tests makes it easier to locate test files and allows using IDE commands such as "Go to Test/Implementation File".

note

This rule highlights test files that import implementation files with the same name (without the _test suffix).

Example

❌ Bad:

// package/lib/src/my_file.dart
// package/test/some_folder/my_file_test.dart // LINT: The location of this file in the 'test' folder does not match the location of the implementation file in the 'lib' folder.

✅ Good:

// package/lib/src/my_file.dart
// package/test/src/my_file_test.dart

Example

Example​

Example