inject.dart VS mobx.dart

Hi! I'm one of the original authors of https://github.com/google/inject.dart, which I think the OP is referring to. And... sorry! We kind of threw some code over the wall and never followed up.

I don't know the .Net DI container, but I forked the old Dart DI lib from a guy from Google and updated it to get it working again. Planned to release soon :-)

Dependency Injection ⇨ Compile-time dependency injection

(disclaimer: I work on the Flutter team and one of the original authors of https://github.com/google/inject.dart, which, while used by internal google teams, hasn't seem much love in the open-source)

Yes but in classic Google fashion it's already been deprecated https://github.com/google/inject.dart

I'll also add that the MobX documentation is a great resource and much better than explaining than I am. If you want to explore a little more I definitely recommend checking it out.

The native way of state management in Jetpack Compose is `mutableStateOf` and `derivedStateOf`. It is an analogue of mobx.dart. Are you familiar with these concepts? What issues did you face with?

· MobX– It’s a popular technique since a long time and uses Observables, Actions and Reactions to notify the widgets of changes. It as initially designed to be used with JavaScript projects and then migrated to Dart to be used used with Flutter projects. It’s an annotation based package which generates the code using a separate package. Read more about it here.

For more examples and guides you can see the original documentation.

Having said that when it came to testing I did not find a good way to write the kind of tests I wanted, although the documentation for mobx in in Flutter is great https://mobx.netlify.app/ I found it lacking when trying to figure out how write robust unit tests. Luckily I found quite a nice approach that I'd like to share in this post.

MobX ⇨ State Management

Active development: low Github link