Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I'm using the new signal-based contentChildren() API in Angular 21.
I expected contentChildren() to behave like any other signal. Specifically, when its value changes after content projection is initialized, any dependent computed or effect should automatically re-run.
However, that does not happen.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
I'm using the new signal-based contentChildren() API in Angular 21.
I expected contentChildren() to behave like any other signal. Specifically, when its value changes after content projection is initialized, any dependent computed or effect should automatically re-run.
However, that does not happen.
Please provide the environment you discovered this bug in (run ng version)
"dependencies": {
"@angular/animations": "^21.2.0",
"@angular/common": "^21.2.0",
"@angular/compiler": "^21.2.0",
"@angular/core": "^21.2.0",
"@angular/forms": "^21.2.0",
"@angular/platform-browser": "^21.2.0",
"@angular/router": "^21.2.0",
"@angular/service-worker": "^21.2.0",
"@primeuix/themes": "^2.0.3",
"angular-svg-icon": "^19.1.1",
"file-saver": "^2.0.5",
"jalali-moment": "^3.3.11",
"jalali-ts": "^8.0.0",
"ng-persian-datepicker": "^10.0.0",
"ngx-spinner": "^21.1.0",
"primeicons": "^7.0.0",
"primeng": "^21.1.9",
"rxjs": "~7.8.0",
"tailwindcss-primeui": "^0.6.1",
"tslib": "^2.3.0"
},
Anything else?
No response
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I'm using the new signal-based contentChildren() API in Angular 21.
I expected contentChildren() to behave like any other signal. Specifically, when its value changes after content projection is initialized, any dependent computed or effect should automatically re-run.
However, that does not happen.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
No response