-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CUSTOM_ELEMENTS_SCHEMA breaks validation for known components #24223
Comments
Yes, that is the correct behavior. We don't know what elements are custom-elements and so we have to disable the validation everywhere. There really is no good way to know which element is custom element and which is not. |
Indeed, when we face some tag we cannot say if it is custom element or just a misspelled tag. But at least we could check if this tag is an angular component and make validation for it :) |
This is still reproducible with the lates Angular v9 running ivy: https://stackblitz.com/edit/angular-ivy-nyg1z7?file=src%2Fapp%2Fapp.component.ts While it is true that during AoT compilation angular/packages/core/src/render3/instructions/shared.ts Lines 1091 to 1105 in ed1b4a8
|
Also relevant: #12045 |
Closing in favor of #12045 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a...
Current behavior
I use angular alongside with custom elements, however if I use CUSTOM_ELEMENTS_SCHEMA it stops validating not only custom elements, but angular components as well
Expected behavior
I'd like validation continue to work for angular components
Minimal reproduction of the problem with instructions
Can't bind to 'foo' since it isn't a known property of 'app-heroes'
app.module.ts
Environment
The text was updated successfully, but these errors were encountered: