Describe the bug
In the docs it says that in the unit tests we should await fixture.whenStable() so a query completes and we get its resulted data. It is true but if I add a class field that references to query.data the query's data becomes undefined.
Your minimal, reproducible example
https://github.com/ms-dosx86/test-when-stable
Steps to reproduce
- Run
ng test
- See that the test passes
- Uncomment the commented line in
app.ts
- Run the test again
- Test fails
Expected behavior
I'm not sure what's going on there but I have a feeling that creating a class field that references to query.data shouldn't cause such behaviour.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
- MacOS 26.0.1 (25A362)
- Chrome 143.0.7499.193
Tanstack Query adapter
angular-query
TanStack Query version
5.90.22
TypeScript version
5.8.2
Additional context
No response
Describe the bug
In the docs it says that in the unit tests we should await
fixture.whenStable()so a query completes and we get its resulted data. It is true but if I add a class field that references toquery.datathe query's data becomesundefined.Your minimal, reproducible example
https://github.com/ms-dosx86/test-when-stable
Steps to reproduce
ng testapp.tsExpected behavior
I'm not sure what's going on there but I have a feeling that creating a class field that references to
query.datashouldn't cause such behaviour.How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Tanstack Query adapter
angular-query
TanStack Query version
5.90.22
TypeScript version
5.8.2
Additional context
No response