There are multiple changes and clarifications in the Promises/A+ v1.1 specification that need to be addressed in the Deft JS Promises implementation. There is a new error condition for which an error needs to be thrown, and there have been clarifications of some of the propagation behavior for chains of then-ables return then-ables in their callbacks.
Yesterday, I updated promise.coffee so that it passes all 862 tests of the Promises/A+ v2.0 test suite. Promise.coffee is essentially a stripped-down reference implementation of Promises/A+ that I created to explore new ideas and as a model for how to decompose Promises/A+ functionality into object-oriented classes. The changes made in promise.coffee v1.0.2 need to migrated to the expanded implementation in Deft JS, and the embedded Promises/A+ test suite needs to be updated to v2.0 to demonstrate compliance with the Promises/A+ v1.1 specification.
There are multiple changes and clarifications in the Promises/A+ v1.1 specification that need to be addressed in the Deft JS Promises implementation. There is a new error condition for which an error needs to be thrown, and there have been clarifications of some of the propagation behavior for chains of then-ables return then-ables in their callbacks.
Yesterday, I updated promise.coffee so that it passes all 862 tests of the Promises/A+ v2.0 test suite. Promise.coffee is essentially a stripped-down reference implementation of Promises/A+ that I created to explore new ideas and as a model for how to decompose Promises/A+ functionality into object-oriented classes. The changes made in promise.coffee v1.0.2 need to migrated to the expanded implementation in Deft JS, and the embedded Promises/A+ test suite needs to be updated to v2.0 to demonstrate compliance with the Promises/A+ v1.1 specification.