-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Garbage collection #41
Comments
Could ES6 |
That's an interesting idea! On the other hand, I think it would be beneficial to be able to inspect via Redux which items are being garbage collected. If items start unexpectedly disappearing from the store, that might be very confusing. I wonder if we can somehow get both. |
Relay got this far without having garbage collection at all, so I think this is a pretty low priority right now. |
I'm closing this since I think we don't need an issue to keep track of this. a) we're not likely to forget this, and b) project notes would be a better place. |
Angular2: Describe service, decorator and examples
In the current code, the store will grow without bound as more and more queries are fetched. We should implement a strategy for clearing out data we are no longer using.
This can be as simple as re-running all of the active queries and putting the results into a new empty store, then throwing away the old one.
The text was updated successfully, but these errors were encountered: