angular 2.0 promise design doc.pdfVIP

AngularJS 2.0 Promise Design Doc Status: Draft Authors: Jeff Cross (crossj@) Objective AngularJS 2.0 needs promise support to build out the core libraries that make up AngularJS, as well as to provide users of AngularJS with a default option for using promises with AngularJS 2.0 apps. ES6 Promises are now a first class citizen of the Web Platform, and are being implemented in major browsers12 ! As such, there is less burden on frameworks to implement all the underpinnings of promises. This document will explore the opportunity to provide APIs to supplement the native implementation to improve developer experience and testing, and will propose a detailed design to be implemented as part of AngularJS 2.0. One challenge posed by having a native implementation of Promise is that the internal mechanisms are now hidden from JavaScript, particularly the queueing and execution of async microtasks, which presents some challenges to the way tests are written. This doc will attempt to identify such issues, and propose solutions. In addition to testing challenges, this doc will explore ways of making Promises more enjoyable to use for end users by exploring different APIs. 1 /forum/#!forum/v8-users 2 /en-US/Firefox/Releases/25 Example ES6 Promise Implementation function doneCounting(val) {   alert(Counted to  + val);   return val; }   function couldNotCount(reason) {   alert(Could not count);   return reason; }   function resolver(resolve, reject) {   setTimeout(function doneCounting() {     resolve(5);   }, 5000); }   var countToFive = new Promise(resolver); countToFive.then(doneCounting, couldNotCount); Requirements As Native As Possible In an ideal world, when developers need the control-flow semantics that promises provide, they would use only the native Promise implementations found in JavaScript runtimes. This design doc should aim