Hi,
This problem has two aspects:
1/ Is there a need to do something that cannot be done using normal
interceptors?
2/ Are there performance reasons why there is a need to extend the API
About 1/, unless I am missing something, there is nothing that cannot be
done right now. It may or may not
with key, value, where can i put the "!important"?
>
>
>
>
> On Fri, Mar 21, 2014 at 4:24 PM, Lucas Galfaso
> > wrote:
>
>> Hi,
>> You can check how the ng-attr directive is used at
>> http://docs.angularjs.org/guide/directive at the section named
Hi,
You can check how the ng-attr directive is used
at http://docs.angularjs.org/guide/directive at the section named "ngAttr
attribute
bindings"
Note: it is not meant to be used for the `style` attribute, in that case
use `ng-style`
-lg
On Friday, March 21, 2014 10:45:30 AM UTC-3, Fernan
Hi,
Update to a newer version of ngResource (one that does provide $promise)
as if you use the old version that you have $rootScope.foos.$promise is
undefined
Regards, lg
On Wednesday, January 15, 2014 6:52:51 PM UTC-3, Lennon Pulda-Grealy wrote:
>
> I should note that since the JSFiddle dire
do
> it). An updated plunk is here:
> http://plnkr.co/edit/51XRoj5jProSiTbM9Gna?p=preview
>
> I'd still like to find a way to avoid hitting the digest limit if
> possible, and a way to avoid "value in value", but without turning the code
> into a procedural blob.
&g
Let me answer inline
On Wednesday, January 8, 2014 9:16:56 PM UTC-3, Alexandros Marinos wrote:
>
> I wanted to create an angular app that could visualise any json file, so
> this explains the need for recursion. I did this with recursive templates.
>
> However, I wanted to be able to extract pot
I think you are looking $scope.$evalAsync
-lucas
On Wednesday, December 18, 2013 7:18:55 PM UTC-3, Benjamin Melki wrote:
>
> Hi,
> from ng repeat items, I can click on each item and it will bring detailed
> page. Then from a back button, I get back to ng repeat, and to preserve
> state, I injec
Hi,
The ngResource API makes the assumption that the elements it is handling
are objects, not strings. When ngResource receives a string, it tries to
transform it to an object the best way it possible, so it is converted to
the object you are seeing.
Regards,
Lucas
On Friday, December 20,
Hi,
- The directive ng-if and every other directive that remove/add DOM
elements involves some performance hit. Try using ng-show that only
adds/removes a class to the element (an operation that is a lot faster).
- Be sure that foo.bar resolves to a boolean value, if this is not the
case, then
