Closed sonatard closed 1 day ago
I'm not sure what you mean by merging apollo-kotlin-normalized-cache into apollo-kotlin-normalized-cache-incubating?
I should make a new release today which includes #48.
The plan is to continue iterating on this repository, and when it is ready for a v1, we'll rename it to remove "incubating", and deprecate the current stable cache.
At the moment though, this repository is not considered stable, which means the APIs may change from one version to the next. The format of the data may also change, so you should assume the cached data may be lost when upgrading. If your app considers the data to be a cache only, that is probably ok, but if you store things like login id, API tokens, for example, it may not be acceptable to lose them.
The plan is to continue iterating on this repository, and when it is ready for a v1, we'll rename it to remove "incubating", and deprecate the current stable cache.
Thank you. This is what I wanted to know. I plan to wait until v1 is released before using #38 and #48.
Is there any plan to merge apollo-kotlin-normalized-cache into apollo-kotlin-normalized-cache-incubating? We are considering using apollo-kotlin-normalized-cache-incubating in production because of issues #48 and #38.