This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
fix($parse): allow for new lines in expr when promise unwrapping is on #4718
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.
Previously, when unwrapping promises was set to
true
, (via$parseProvider.unwrapPromises(true);
)an error would occur if a parsed expression had a new line in it.
This was because when generating the
evaledFnGetter
code,a new line in an parsed expression would create a new line in a JS string in that code, which is illegal.
That is:
Plunk with 1.2.0-rc.3: http://plnkr.co/edit/QHJHkQOViLYQYNveMnVL?p=preview
Plunk with this PR: http://plnkr.co/edit/sI1e4vCSw4HBZnjitojG?p=preview