-
Notifications
You must be signed in to change notification settings - Fork 26.3k
feat(common): accept undefined inputs in NgTemplateOutlet #61404
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
Conversation
Extend types of inputs to include `undefined` to avoid `?? null` when using singals (e.g. `viewChild`). Fixes angular#51225
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed-for: public-api
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Reviewed-for: fw-general
Reviewed-for: public-api
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth a breaking change note when people are relying on the type of those public variables?
Reviewed-for: public-api
@devversion You're making a good point. If we consider it a breaking change we won't be able to land it in v20. Maybe let the TGP decide if we consider that breaking ? |
TGP is "Green" without having to cleanup g3. I think we can consider this change non breaking. |
This PR was merged into the repository by commit 82327f2. The changes were merged into the following branches: main, 20.0.x |
Extend types of inputs to include
undefined
to avoid?? null
when using singals (e.g.viewChild
).Fixes #51225
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Inputs don't accept
undefined
Issue Number: #51225
What is the new behavior?
Accept
undefined
Does this PR introduce a breaking change?
Other information