Chirayu Krishnappa 9577702e8d fix($resource): don't use $parse for @dotted.member ... params and paramDefaults support looking up the parameter value from the data object. The syntax for that is `@nested.property.name`. Currently, $resource uses $parse to do this. This is too liberal (you can use values like `@a=b` or `@a | filter` and have it work - which doesn't really make sense). It also puts up a dependency on $parse which is has restrictions to secure expressions used in templates. The value here, though a string, is specified in Javascript code and shouldn't have those restrictions.		2013-11-11 16:17:34 -08:00
..
badargs.ngdoc	style(minerr): prefer component name as namespace	2013-08-09 14:12:04 -07:00
badcfg.ngdoc	style(minerr): prefer component name as namespace	2013-08-09 14:12:04 -07:00
badmember.ngdoc	fix($resource): don't use $parse for @dotted.member	2013-11-11 16:17:34 -08:00
badname.ngdoc	fix(*): protect calls to hasOwnProperty in public API	2013-10-07 09:01:13 -07:00