-
Notifications
You must be signed in to change notification settings - Fork 27k
Closed
Labels
area: upgradeIssues related to AngularJS → Angular upgrade APIsIssues related to AngularJS → Angular upgrade APIscore: inputs / outputscross-cutting: signals
Milestone
Description
Which @angular/* package(s) are the source of the bug?
upgrade
Is this a regression?
Yes
Description
Components which use signal based inputs do not work as expected with downgradeComponent(). Looks like the DowngradeComponentAdapter is incorrectly setting inputs here and should probably use the componentRef.setInput(prop, value) instead.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Due to the way the input is being set, the value ends up being the actual raw value rather than the signal. This causes a not a function error when we try to call and grab the value from the signal.
Please provide the environment you discovered this bug in (run ng version)
No response
Anything else?
No response
Metadata
Metadata
Assignees
Labels
area: upgradeIssues related to AngularJS → Angular upgrade APIsIssues related to AngularJS → Angular upgrade APIscore: inputs / outputscross-cutting: signals
Type
Projects
Status
Done