feat(hydrated_bloc): use user provided storage in hydrated cubit

[elias8]

Status

READY

Breaking Changes

NO

Description

• Resolves [Feature Request] Hydrated blocs with different storages in the same app #1421 as I suggested the implementation in the comment

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[dolsem]

Any status update on this? Would be great to have this feature!

[felangel]

Rather than injecting a storage into specific blocs I'd prefer to experiment with a HydratedStorageProvider that scopes different storage implementations to different parts of the widget tree. I was planning to revisit this within the next week or so (once v7.2.0 is out and a v8.0.0-dev release is published).

[elias8]

@felangel I think that is a better approach! 👍

[felangel]

Closing this PR for now in favor of the HydratedStorageProvider approach. I'll try to get to this in the next few days as part of the v8.0.0 release 👍

[dolsem]

@felangel would it be possible to use multiple storage providers with different blocs within the same widget? My use case is using flutter_secure_storage for auth tokens (auth cubit), and default storage for all other app data.

[felangel]

@felangel would it be possible to use multiple storage providers with different blocs within the same widget? My use case is using flutter_secure_storage for auth tokens (auth cubit), and default storage for all other app data.

In that particular case you'd need to split the auth cubit BlocProvider into its own widget but I also don't recommend managing auth tokens in cubits/blocs. In my opinion, those should be managed by the networking layer using something like fresh_dio. Hope that helps 👍

[dolsem]

@felangel I see, interesting. I'll give fresh_dio a try, thanks!