HI! I am Tomas. 👋 Mobile engineer in MedTech and data science enthusiast. Sharing insights on Flutter, Android, Python, and any helpful tips for tech and life. Follow for more 👆

These two saved me countless hours of debugging when I forgot to add a simple `await` to a method. At some point, if you want to do something with the result, you have to await it. Missing it can lead to uncaught errors or race conditions.

If you've got a Gradle process randomly stuck in the background as I did today, save yourself the headache. Here's the fix:

If you have some implementations and generated files that you do not want to include in test coverage. You can add them in settings under `dart.coverageExcludePatterns`. Available in v3.118 VSCode Dart extension.

In the Flutter VSCode extension v3.118, you can see widget previews directly in the IDE. This feature is still experimental, so you must enable it manually and switch to the master channel of Flutter. Hopefully, it will soon be polished and become part of the stable version!

If you use a monorepo, you can run Dart linters and AI agents across multiple packages and apps Useful use cases: - documentation - unified coding style - refactoring with the help of AI - adding new linter rules with a fix available - searching for pitfalls/explanations in code

A couple of ways you can automate a monorepo with multiple packages/projects with Melos: - running build runner - testing unit tests/integration tests - generating API endpoints - creating licensing files for export

https://t.co/Z7TdBaNYvs

Melos is a package that simplifies handling and automating monorepo Flutter projects. You can define custom scripts and execute them across multiple apps and packages easily, avoiding repetition. It streamlines running scripts on the entire codebase from CI/CD, too. Link in 🧵

A Flutter monorepo simplifies developing apps/packages on a shared foundation Code/dependency changes propagate across the codebase in the analyzer. It forces you to maintain apps while you are making breaking changes. With a pubspec workspace, you can do the following:

Navigating directories can reduce friction when solving problems. I still recall discovering the `cd -` command, which allows you to toggle back to the previous directory in the terminal. Tools like zoxide are better, but for simple tasks, it remains relevant.

I created an issue on GitHub comparing the solution to the Android Previews, which you can stack together. It simplifies the creation of previews afterwards, as you can use your annotations and generate multiple previews instantly. https://t.co/EhzubfbIwR

Here's an example of customizations for the experimental preview in Flutter, featuring multiple properties, including wrappers, themes, locales, and more. It covers the basics, but hopefully, in the final version, there will be a way to reuse annotations for multiple widgets.

If you build a large app or work at a company, you likely end up splitting parts into packages and using custom tags for them. In Dart 3.9/Flutter 3.35.0 and higher, you can now parse the tag and deviate versioning from it, similar to other packages.

With Dart 3.9 / Flutter 3.35.0 and higher, you can apply a switch on the type linter rule. Avoid using runtime types if pattern matching is available. If classes change their hierarchies, it can lead to weird bugs.

In Flutter 3.35.0 and higher, you can experiment with widget previews in the browser You can provide themes, light/dark mode, widget wrappers, localizations, and interact with widgets individually Still, it is an experimental feature, so breaking changes are to be expected

local_auth_darwin now supports more granular handling of unhappy paths at version 1.6.0 You can now handle disabled biometry, user fallback, and authentication cancellation by extending error codes. The codes are not defined at local_auth in the meantime.

I see many people recreating the HTTP client whenever it is needed. Each new client can open new network connections, which is slow, resource-intensive, and will slow down other requests. Create one client and use it everywhere.

AbortTrigger can be any future. For example, if the user finishes some task before all the loading finishes, you can bind the calls to one Completer or another Future. If it finishes, all the calls will halt.

The http package has finally started to support request cancellation, from version 1.5.0 You can accompany your request with a Future or Completer. Whenever you no longer need a response, simply finish it. Finishing throws an exception, so take care of it appropriately.

My favorite pattern for clean, accessible logging. Define this mixin once, and get a consistent logger instance in any class. No more manual instantiation.