Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Revert "fix($parse): standardize one-time literal vs non-literal and interceptors" #15958

Merged
merged 1 commit into from
Jun 20, 2017

Conversation

jbedard
Copy link
Collaborator

@jbedard jbedard commented May 3, 2017

Reverts 60394a9 to fix #15905 in 1.6. Currently plan is to NOT revert in 1.7.

Fixes #15905

Copy link
Member

@gkalpak gkalpak left a 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).

@jbedard
Copy link
Collaborator Author

jbedard commented May 3, 2017

Created #15960

@jbedard
Copy link
Collaborator Author

jbedard commented May 9, 2017

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...

@gkalpak gkalpak added this to the 1.6.5 milestone May 19, 2017
@Narretz
Copy link
Contributor

Narretz commented May 31, 2017

What's the status of this now that #15964 has been fixed?

@jbedard
Copy link
Collaborator Author

jbedard commented May 31, 2017

#15964 fixed filters, #16018 does the same for interceptors (like the one in ng-class). I'm leaning toward still reverting the ng-class part of 189461f in 1.6 just to avoid unexpected changes in 1.6 (no longer deep watching one-time bindings in ng-class), but that's debatable...

@Narretz
Copy link
Contributor

Narretz commented Jun 15, 2017

This looks like the last PR needed to get 1.6.5 out of the door, ist thart right?

@jbedard
Copy link
Collaborator Author

jbedard commented Jun 16, 2017

Note that #15905 was properly fixed in 1.6, so this revert now only restores the "deep watch of one-time bindings in ng-class". I keep trying to find a way revert that without reverting the parse.js changes, but that isn't proving easy. So yeah I think we should just revert this in 1.6. Feel free to merge if you agree...

@jbedard
Copy link
Collaborator Author

jbedard commented Jun 16, 2017

Ok now that I've found #16059 we have to do this revert (or #16015!) in 1.6...

@Narretz
Copy link
Contributor

Narretz commented Jun 16, 2017

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

@jbedard
Copy link
Collaborator Author

jbedard commented Jun 17, 2017

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.

@Narretz
Copy link
Contributor

Narretz commented Jun 19, 2017

LGTM. Please revert and merge #16059 too

@jbedard jbedard merged commit f003d93 into angular:v1.6.x Jun 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants