registering tracker might requre a revision

[vetik32]

scenario a face the issue.
http://plnkr.co/edit/XU0tvWsfKcuJPL9oXyCh

has a simple ui router, (I guess same story with ngroute)

with original promise-tracker I get:
Error: Tracker with id "loadingTracker" already exists!

Long story short, when switching from view/controller to another then return back, we face errors because of -reregistering same promises/trackerId.

what's the way it should be done? use the plnkr link to see what I mean.

also I'll create a pull request to show the mods that addresses the issue for me.

p.s. I didn't run the tests from the project.

[ajoslin]

Hi @vetik32 - now you use promiseTracker.register(id) to create a tracker, then promiseTracker(id) to get it.

[ajoslin]

Plunkr fixed - http://plnkr.co/edit/ciQLISuC40Ay2gVFDnGG?p=preview

The whole ID system will probably be removed before 2.0, though.

[vetik32]

thanks for a quick reply. I don't quite fill ok with registering all possible trackers on bootstrapping.
I'm using it with angular-busy directive. will think it over, thanks.

[ajoslin]

Well you don't have to do it on bootstrap, just somewhere it will only happen once.