This repository was archived by the owner on Apr 12, 2024. It is now read-only.
fix($parse): fix infinite digest errors when watching objects with .valueOf in literals #15867
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…alueOf in literals
gkalpak
approved these changes
Mar 29, 2017
Narretz
pushed a commit
that referenced
this pull request
Mar 31, 2017
…alueOf in literals Closes #15867
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think this is an edge case of 7084dec (and 1.6.x) that was not handled. If those objects (in the literals) have a
.valueOffunction that returns something other thenthisit will cause an infinite digest.This should probably also go into 1.6?