-
Notifications
You must be signed in to change notification settings - Fork 27k
Closed
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimearea: elementsIssues related to Angular ElementsIssues related to Angular Elementscore: inputs / outputscross-cutting: signals
Milestone
Description
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
lets suppose we have this component :
@Component({standalone: true, ...])
export class ToBeAWebComponent {
anInput = input<string>();
}by using the @angular/elements package I can export that component as a web-component named : to-be-a-web-component.
const wc = document.querySelector("to-be-a-web-component");
wc.anInput = "aValue"; // this will create a bug and change the type of anInput from InputSignal to string.
// and if the input value is referenced in the template, or any other place, an error will be raised telling that anInput is not a function Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Angular CLI 17.1.0
@angular/core 17.1.0
Anything else?
No response
chintankavathia, saithis, attilacsanyi, ManuelRauber, darinw and 24 moremouadennaciri, kkachniarz220, saithis, attilacsanyi, webcoderr and 5 more
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimearea: elementsIssues related to Angular ElementsIssues related to Angular Elementscore: inputs / outputscross-cutting: signals
Type
Projects
Status
Done