Add specific entrypoint for usage with Riverbloc / Riverpod (WIP)

kranfix / riverbloc

`flutter_bloc` implemented with `riverpod` instead of `provider`.

83 stars 17 forks source link

Add specific entrypoint for usage with Riverbloc / Riverpod (WIP) #37

Closed tlvenn closed 3 years ago

tlvenn commented 3 years ago

This library entrypoint does not explicitly import flutter_bloc or its hook and therefore its BuildContext extensions that compete with riverpod's ones.

TODO:

[ ] Decide if we want to remove 'useRiverBloc` from the export list in the existing entrypoint (Breaking change)
[ ] Add documentation for the new entrypoint

Fixes #35

tlvenn commented 3 years ago

For now, I did not remove the useRiverBloc export from the original entrypoint as to not create some breaking change. It is something we could consider to provide a clearer path of usage.

Once we are set on this, I can also push a commit to document that new entrypoint. Let me know what you think @kranfix.

Thanks !

tlvenn commented 3 years ago

Actually I just realized that such entrypoint actually already exist, i saw it before but was confused by its content, mainly the fact that it also exports 'useBlock`.