Flutter Bad Code Smells

In the article, Why DO We Need Flutter Lints:

Why Do We Need Flutter Lints

I covered how the lints we apply serve to become the second Dart-Compiler in highlighting to the compiler what our programming intents are. But such things only get rid of code antipatterns at the code level. What tool can we use to get rid of the antipatterns at the OOP Architecture level?

That tool is Dart Code Metrics and like Lint Rules and the Linter; it also plugs into the Dart anlayzer to run every time the compiler performs a build. Let me show you how to configure the tool and how to use it to make good OOP Architecture decisions about your Flutter Application implementation.

The Dart Code Metrics Package

The Dart Code Metrics Package:

dart_code_metrics | Dart Package