Flutter DevOPS Secrets, Code Linting

The beginning of flutter app development begins with having a proper strategy of linting and applying the proper lint rules and is the first step of creating a DevOps strategy and DevOPS system for flutter app development. In this article, I cover why we do code linting and cover a more opinionated lint rule set-up.

Why Do We Need To Code Lint

Okay, so why do we have to-lint clean our code. The way compilers work for typed languages such as Dart is that check some rules that they can compute fast as far as code paths and leave other checks to the execution of static checking and developer corrections.

And, the twist is that while the Flutter SDK and Dart SDK teams came up with a lint-rule list, we actually need to further. So why do we need to go further?

1. The Dart Typed approach to computer typed language is still evolving. I have found through past migrations such as from not-null-safe to null-safe that extra lint analyzer guard rails better prepare code to be migrated with no headaches and no work at all.

2. By using more lint rules than the minimum that the Flutter SDK team recommends we can get better cleaner code as far as clearly expressing our programming intent.