FeatureRequest: support for ordered initialization of an angular app with asynchronous data

[leifhanack]

Hi there,

again and again I see people asking for a solution to do things after the app is initialized.

E.g. this latest thread or this thread which we created.

We have had the same issue and solved it with a 'init-service'. Here is the sample init service and it's detailed documentation.

It would be awesome if we have a build-in support for this reoccurring request. Or should it be sufficient to use the routeprovider and it's resolve block?

Regards, Leif

[gesellix]

👍

There are several forum threads regarding "angular initialization" issues, are there any plans of the angular core team to add a configurable initialization feature?

[leifhanack]

There is another thread in the google group: https://groups.google.com/forum/m/#!msg/angular/F5yoJevAHNg/qPeMgI5y420J

[malixsys]

Doesn't ui-router's resolve functionality cover this?

[thardy]

It does not. Resolve has to be added to EVERY controller where it's needed. Most of the discussion has been about data that is needed by every controller. It's a serious pain and not at all elegant to add the same list of resolve's to every controller. Other frameworks handle this with a global resolve. I'd be happy with a global resolve.

[malixsys]

You can easily inherit the configuration...

Something like:
http://jsbin.com/reh/3/edit

[michaelhunziker]

Plus 1

[gesellix]

Similarly to the resolve on controller level, PR #3295 makes dependency injection resolve lazily by returning promises from service factories.

[czjvic]

+1

[airandfingers]

+1

[flockonus]

👍

[steffanhalv]

@malixsys Same problem there. You also include promise to every controller, which makes the code ugly. We need a common initializer which has promise to be resolved before any controller is run.

+1

[fibinger]

+1

[tony-kerz]

👍