AngularJS是否承诺调度可与`async` /`await`一起使用？

Question

TypeScript constantly suggests that I change my AngularJS service code to async / await functions.

My understanding is that using the await keyword is totally fine with third-party promises, since it is just syntax sugar for calling then . However, I normally return Angular promises because they are necessary to play nicely with the digest cycle.

This code gives me an error because async functions wrap their contents in an ES6 promise. Will this matter for Angular scheduling, given that the returned promise is still hooked up to an Angular-spawned promise? Or should I submit an issue to TypeScript for suggesting async / await when functions do not explicitly return an ES6 promise?

Answer 1

For anyone viewing this in the future. It does not play nicely. async functions wrap their contents in a global ES6 promise, so if you await AngularJS promises within the changes will eventually hit, but scheduling is weird when you chain together $q promises and ES6 promises, so there will usually be an artificial delay before changes are reflected in the DOM.

On the other hand, Angular 2+ monkey-patches DOM event sources and promises, so async-await should work as expected with newer versions.