Publish to my blog (weekly)

• Top 16 Dart Tips and Tricks Every Flutter Developer Should Know

  • returned as an Iterable
  • returns a Stream

• Control your Flutter app on the fly with Firebase Remote Config | kazlauskas.dev

  • eventRepository
  • eventRepositoryProvider

• Flutter Shopping App prototype: Lessons learned | kazlauskas.dev

  • When implementing BLoCs for the prototype, I started adding tests BEFORE the actual map-event-to-state logic. The reason is simple - I knew which output is expected on the corresponding input, so I wrote all the possible input/output test cases first. Of course, all the tests were failing, but after implementing the actual BLoC logic, all of them turned green and I was sure that the final result is just what I expected in the beginning.
  • I implemented the UI first and only then added tests. The reason is simple - it is just easier this way. To me, widget tests ensure that I won't break the UI in the future while adding new features, so I prefer covering only the "final" UI code with tests.

Posted from Diigo. The rest of my favorite links are here.