Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
When "chaining" two resources (by using the value of the first resource in the request of the second resource) something weird happens: The value of the first resource suddenly seems to be always undefined, as long as the request of the second resource is some kind of "computation" and not just the value itself.
Please provide a link to a minimal reproduction of the bug
https://github.com/rmeyergh/resource-bug/blob/main/src/app/app.component.ts
Please provide the exception or error you saw
myOtherResource.value() in the given example produces "undefinedbaz" instead of "foobarbaz".
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 19.1.8
Node: 22.9.0
Package Manager: npm 11.0.0
OS: darwin arm64
Angular: 19.1.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1901.8
@angular-devkit/build-angular 19.1.8
@angular-devkit/core 19.1.8
@angular-devkit/schematics 19.1.8
@angular/cli 19.1.8
@schematics/angular 19.1.8
rxjs 7.8.2
typescript 5.7.3
zone.js 0.15.0
Anything else?
No response
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
When "chaining" two resources (by using the value of the first resource in the request of the second resource) something weird happens: The value of the first resource suddenly seems to be always undefined, as long as the request of the second resource is some kind of "computation" and not just the value itself.
Please provide a link to a minimal reproduction of the bug
https://github.com/rmeyergh/resource-bug/blob/main/src/app/app.component.ts
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
No response