I understand that I need to indicate a "key" in the dw-loading attribute (e.g. dw-loading="foo", so that later I can turn on the loading indicator by calling $loading.start("foo").
But I'm using component-organized Angular (as is now recommended), and I have a Bar component, perhaps I will place two or three Bar components on the page at the same time, if they all use dw-loading="foo" will this confuse the angular-loading library? If I call $loading.start("foo") will it turn on the loading indicator just for that instance of the component, for that scope, or will it turn on the loading indicator for all the components (because they all use the same dw-loading key)?
I understand that I need to indicate a "key" in the
dw-loadingattribute (e.g.dw-loading="foo", so that later I can turn on the loading indicator by calling$loading.start("foo").But I'm using component-organized Angular (as is now recommended), and I have a
Barcomponent, perhaps I will place two or threeBarcomponents on the page at the same time, if they all usedw-loading="foo"will this confuse the angular-loading library? If I call$loading.start("foo")will it turn on the loading indicator just for that instance of the component, for that scope, or will it turn on the loading indicator for all the components (because they all use the same dw-loading key)?