Conflicting extensions ModularWatchExtension & Provider:ReadContext

[adamstyrc]

Project Name
flutter_modular

Is your feature request related to a problem? Please describe.
Conflict with lib extension at: https://pub.dev/packages/provider

Me & my team finds it tedious that always when using context.read<T>() we are asked for import by IDE then we always have to choose if using provider.dart or flutter_modular.dart because extensions ReadContext on BuildContext is in conflict with ModularWatchExtension on BuildContext.
Also, when importing both flutter_modular.dart and provider.dart in a file, there is ambiguous extension call so you have to either hide extension from import or use explicit ReadContext(context).read<T> and ModularWatchExtension(context).read<T>

Describe the solution you'd like
Set different and more verbose naming not being in conflict with Provider context.read<T> like readDependency or watchDependency

Describe alternatives you've considered
Just move extension ModularWatchExtension on BuildContext to another file that needs explicit import call and not be included in global flutter_modular.dart exports.

Additional context

Screenshots

[eduardoflorence]

Duplicate of #670

[adamstyrc]

Well, it's just half duplicate because my point of view is that still you always have to think what you import and add show Modular (or btw hide ModularWatchExtension). Using Provider read/watch is really heavy in our project.
I more liked your approach @eduardoflorence that we change naming from read and watch to readBind / watchBind :)

Could we consider that?

[jacobaraujo7]

duplicate