> Not necessarily - if you're using new DOM APIs which > return promises, then you need to upgrade your libraries. > Libraries are easy to upgrade. A crummy legacy is not.
Okay, so how will end users or jQuery authors upgrade their promises to become ES6-compliant? On Fri, Dec 20, 2013 at 5:45 PM, Kevin Smith <[email protected]> wrote: > Here is code that breaks with that solution: ``` function >> createParser(code) { return {then: chainedTransformation => { ...; return >> this; } } } waitForFormSubmit() .then(e => $.get(getUrlFromUrlField())) >> .then(code => createParser(code, options)) ``` > > > Not necessarily - if you're using new DOM APIs which return promises, then > you need to upgrade your libraries. Libraries are easy to upgrade. A > crummy legacy is not. > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
