Skip to content

Conversation

JeanMeche
Copy link
Member

…indings

Typechecking for those expression is non-obvious and developers should be using separate input/output bindings

BREAKIND CHANGE: Use separate input/output bindings instead.

fixes #59116

WIP: Will require a cleanup first.

@angular-robot angular-robot bot added detected: feature PR contains a feature commit area: compiler Issues related to `ngc`, Angular's template compiler labels Sep 1, 2025
@ngbot ngbot bot modified the milestone: Backlog Sep 1, 2025
…indings

Typechecking for those expression is non-obvious and developers should be using separate input/output bindings

BREAKIND CHANGE: Use separate input/output bindings instead.

fixes angular#59116
@JeanMeche JeanMeche force-pushed the 2way-binding-non-null branch from 7bfbf1d to d152c48 Compare September 1, 2025 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: compiler Issues related to `ngc`, Angular's template compiler detected: feature PR contains a feature commit
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove support for non-null assertions from two-way bindings
1 participant