You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fresh should export a Storage interface which means it can work with any storage provider. Out of the box, it should come with its own implementation: FreshTokenStorage, based on Hive.
#28
Open
akasher opened this issue
Aug 12, 2020
· 0 comments
Currently fresh allows the user to store tokens in which every token storage they may choose.
What if fresh acted a little bit like HydratedBloc and provided a HydratedBlocStorage which is based on Hive.
And additionally the end user should be given an option to extend HydratedStorage to use whichever storage media they choose.
For my private project I have extended OAuth2Token and created a new Token class and corresponding type adapter which can be stored in Hive.
And Extended TokenStorage to create a HiveTokenStorage.
The text was updated successfully, but these errors were encountered:
akasher
changed the title
Fresh Should Provide HiveTokenStorage like HydratedBloc provides HydratedStorage.
Fresh should export a Storage interface which means it can work with any storage provider. Out of the box, it should come with its own implementation: FreshTokenStorage, based on Hive.
Aug 12, 2020
Currently fresh allows the user to store tokens in which every token storage they may choose.
What if fresh acted a little bit like HydratedBloc and provided a HydratedBlocStorage which is based on Hive.
And additionally the end user should be given an option to extend HydratedStorage to use whichever storage media they choose.
For my private project I have extended OAuth2Token and created a new Token class and corresponding type adapter which can be stored in Hive.
And Extended TokenStorage to create a HiveTokenStorage.
The text was updated successfully, but these errors were encountered: