Bloc: is it really necessary to change the interfaces all the time

[gustavobrian]

Hello, if the best library is becoming a problem, is it really necessary to change the interfaces all the time?
I appreciate the work, but this library is becoming a problem for me.

[felangel]

Hi @gustavobrian 👋
Thanks for opening an issue!

Can you provide a bit more context? Is there a particular change(s) you’re referring to? Sorry for the inconvenience!

[narcodico]

Changes to packages are always a bit annoying for anyone, but in order to polish a library change must happen. Surely you're not going to complain when you'll be able to write a time machine using 3 lines of code.

[felangel]

Closing for now since there isn't enough context for me to address this. I just want to add that you should specify versions in your pubspec like:

dependencies:
  flutter_bloc: ^2.0.0

This will ensure that you get all non-breaking updates but when v3.0.0 comes out you will not be forced to upgrade (it's up to you when to manually update the version in your pubspec to ^3.0.0).

If you just have something like:

dependencies:
  flutter_bloc:

or

dependencies:
  flutter_bloc: any

Then you might have breaking changes when you do a flutter packages get.

As @RollyPeres mentioned, the changes are all done in order to fix bugs or add features which ultimately should improve the developer experience. With that being said, you should never feel forced to upgrade. There's nothing wrong with specifying an exact version in your pubspec.yaml if you don't want to take any chances with upgrades.

dependencies:
  flutter_bloc: 2.0.0

In addition, if you're working on an app then it's recommended to check in your pubspec.lock to source control. This will ensure that everyone who pulls the code and runs a flutter packages get will have the same versions of the dependencies.

Hope that helps and feel free to add additional information and I'm happy to continue the conversation 👍