-
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
Fixed issue with multiple polling queries #262
Conversation
@@ -94,7 +94,7 @@ export class QueryManager { | |||
private networkInterface: NetworkInterface; | |||
private store: ApolloStore; | |||
private reduxRootKey: string; | |||
private pollingTimer: NodeJS.Timer | any; // oddity in typescript | |||
private pollingTimers: {[queryId: string]: NodeJS.Timer | any}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remind me, why does this have to have an any
? If it's an oddity in typescript, maybe we should keep that explanation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really know why. I will find out and add in an explanation.
This is great! Just wondering if we can cut the time necessary for the test. |
@Poincare this is a great improvement |
Rebased. |
…bject added docs for default dataIdFromObject selector
Since we were using a single timer reference, there were polling leaks when we had multiple polling queries - see #248
This changeset should fix that issue and introduces a unit test that used to fail but now doesn't.
TODO: