-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Revert "fix($parse): standardize one-time literal vs non-literal and interceptors" #15958
Conversation
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, but can you create an issue on the 1.7.0 milestone for documenting the breaking change on 17.x (I am not sure what exactly we have broken, but I understand we have broken some usecase).
Created #15960 |
Note that fixing #15964 should actually fix the issue in 1.6, so it might still be possible to fix this in 1.6 without reverting anything... |
What's the status of this now that #15964 has been fixed? |
…interceptors" This reverts commit 60394a9.
This looks like the last PR needed to get 1.6.5 out of the door, ist thart right? |
Note that #15905 was properly fixed in 1.6, so this revert now only restores the "deep watch of one-time bindings in |
So what you are saying is, to restore " "deep watch of one-time bindings in ng-class" we can either merge or both of
(their respective 1.6 versions) I assume by reverting we err on the safe side? Because we want to remove the deep watch in master anyway |
It's actually
or both of
While I really don't like reverting things, we should probably go the revert route for 1.6... If you're ok with #16059 in 1.6 I can merge those 2 this weekend. |
LGTM. Please revert and merge #16059 too |
Reverts 60394a9 to fix #15905 in 1.6. Currently plan is to NOT revert in 1.7.
Fixes #15905