flutter-tdd-clean-architecture-course VS plugins

TDD in Flutter - Series on test driven development

TDD

This is inspired by ReSo Coder's Clean Architecture tutorial.

So I just finished this course on Clean-Code TDD with Flutter and I'm interested in applying some of the stuff I learned from it to my React projects. One of the neat things in the project was the injection_container.dart file. Seemed like a nice way to consolidate dependencies. Reminded me of the "barrel files" I've seen used in some other project tutorials I've done.

You are using reso's version so I will use this to demonstrate my thoughts.

(This new version will be endorsed by google_sign_in: ^6.0.0, once this PR lands: https://github.com/flutter/plugins/pull/7191, probably next week. This was made a major version change so people can test and update at their own pace.)

Looking at the web version of the video player package which doesn't use textures but VideoElement DOM nodes, I'd guess that textures aren't supported.

It's not 100% true that Flutter doesn't offer any first party native features. These plugins are maintained by the Flutter team: https://github.com/flutter/plugins/tree/main/packages

Here's an example: https://github.com/flutter/plugins. As you can see, that repo has no "issues" tab. And it mentions that issues should be created on the Flutter repo itself

There's work in progress to create a new camera plugin using CameraX: https://github.com/flutter/plugins/pull/6158

Find the example wiring in the Google sign-in example application.

image_picker

shared_preferences

The plugins is missing Issues tab currently. It's hard for developers who need to raise or find issues on packages.