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

$eval array expression with locals returns wrong #5838

Closed
derekhu opened this issue Jan 16, 2014 · 0 comments
Closed

$eval array expression with locals returns wrong #5838

derekhu opened this issue Jan 16, 2014 · 0 comments

Comments

@derekhu
Copy link

derekhu commented Jan 16, 2014

$scope.a = [ {b : 'scope'} ];

$scope.$eval("a[0].b", {b : 'locals'}); // Expect returns 'scope' but returns 'locals'

$scope.$eval("a[0].b", {c : 'locals'}); // Returns 'scope' as expect.
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Jan 17, 2014
@lgalfaso
fix($parse): do not use locals on field access
353371e 
Do not use the locals when performing a field access

Closes angular#5838
@lgalfaso lgalfaso mentioned this issue Jan 17, 2014
Closed
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Jan 17, 2014
@lgalfaso
fix($parse): do not use locals on field access
80866b1 
Do not use the locals when performing a field access

Closes angular#5838
@caitp caitp closed this as completed in 2068d76 Jan 22, 2014
caitp pushed a commit that referenced this issue Jan 22, 2014
@lgalfaso @caitp
fix($parse): do not use locals to resolve object properties
f09b6aa 
Do not use the locals when performing a field access in an angular expression.

Closes #5838
Closes #5862
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix($parse): do not use locals on field access lgalfaso/angular.js
1 participant
@derekhu