You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating @apollo/client (from v.3.8.10 to v.3.9.xx) we have pending timers in our tests using fakeAsync. I am not 100% sure if this is a problem which only occurs using the testing utils (apollo-angular/testing).
To Reproduce
The following code snippet has no pending timers using @apollo/client v.3.8.10. After updating to v.3.9.xx is has 3 pending timers.
it('should have no pending timers', fakeAsync(() => {
const apollo = TestBed.inject(Apollo)
apollo
.query<SomeQueryType>({
query: SomeQuery,
variables: { id: someUuid },
errorPolicy: 'all',
})
.subscribe(() => console.log('value changed'))
apolloCtrl.expectOne(extractOperationNameFromQuery(SomeQuery)).flush(SomeQueryPayload)
tick()
}))
I experienced the same behavior change. But since apollo-angular did not change anything, I expect this should be reported to @apollo/client, not here.
In the meantime, you can use flush(); at the end of your tests, as a workaround to discard those pending timers.
Describe the bug
After updating @apollo/client (from v.3.8.10 to v.3.9.xx) we have pending timers in our tests using fakeAsync. I am not 100% sure if this is a problem which only occurs using the testing utils (apollo-angular/testing).
To Reproduce
The following code snippet has no pending timers using @apollo/client v.3.8.10. After updating to v.3.9.xx is has 3 pending timers.
Expected behavior
There should be no timers pending
Environment:
Additional context
The text was updated successfully, but these errors were encountered: