-
Notifications
You must be signed in to change notification settings - Fork 660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a garbage collector to remove unreachable nodes #3805
Comments
As a note from our team discussion today we talked about doing some more product discovery around the use cases of garbage collection to better understand it's intended use. I'll work on an internal document that will help to define our approach to collecting that feedback from our users and customers. cc @martinbonnin @BoD |
👋 I've pinned this issue to to repo, as we are looking for feedback on what type of use cases people may have around Garbage Collection and our Kotlin Client. |
Feedback Wanted
Implement a garbage collector to remove unreachable nodes
Feedback Wanted
Implement a garbage collector to remove unreachable nodes
Closing in favor of apollographql/apollo-kotlin-normalized-cache-incubating#83 |
(Dangling references are also an issue but related to low level usages of
remove(id)
, see apollographql/apollo-kotlin-normalized-cache-incubating#85)The text was updated successfully, but these errors were encountered: