Open vasilich6107 opened 2 years ago
@vincenzopalazzo sounds like a good candidate for the major release.
Yeah, it is a good point.
I can take a look when I'm back in the office next week!
Hi, I am wondering if this has gotten any traction or what the recommendation is? I see the referenced story to make the store async was closed.
There is some discussion around it, but I need to find the time to test it, if someone what start to test it PR are welcome
Hi. Could you provide any updates on this issue?
Hi, sorry but I did not yet had the opportunity to look into it, also there is this discussion that is going on https://github.com/zino-hofmann/graphql-flutter/discussions/1286 maybe would you participate into it and give your opinion?
Hi @vincenzopalazzo
There is a suggestion to support isar
lib. This is could be a good addition to the cache management diversity but it does not relates to the current issue)
Could you clarify the idea behind looking into isaar
instead of making Store.get
async?
@vincenzopalazzo While support for isar
is good for some folks, seems like rebuilding Store
implementation to support async operations would be a good first step for the project. This way Hive.lazyBox
, isar
, or whatever store someone wants to use could be supported.
We're using Hive at the moment and ran into memory issues because it wasn't immediately clear that Hive places everything into memory unless a developer uses Hive.lazyBox
.
any updates on this?
Describe the solution you'd like During the app functioning the cache could have a lot of data saved. Default HiveBox reads all cache into memory while opening. This could take too much time to wait on application startup. While
Store.get
method issync
there is no way to use lazy boxes.Could you clarify if there is any ideas to implement async store to enable using the lazybox or sqllite for better cache performance?