domenic at domenicdenicola.com (2014-01-03T17:08:43.009Z)
On Fri, Dec 20, 2013 at 12:24 PM, Gorgi Kosev <gorgi.kosev at gmail.com> wrote: > Okay, so how will end users or jQuery authors upgrade their promises to > become ES6-compliant? Still early, but follow here: http://bugs.jquery.com/ticket/14510
On Fri, Dec 20, 2013 at 12:24 PM, Gorgi Kosev <gorgi.kosev at gmail.com> wrote: > > 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? > > Still early, but follow here: http://bugs.jquery.com/ticket/14510 Rick > > On Fri, Dec 20, 2013 at 5:45 PM, Kevin Smith <zenparsing at gmail.com> 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 >> es-discuss at mozilla.org >> https://mail.mozilla.org/listinfo/es-discuss >> >> > > _______________________________________________ > es-discuss mailing list > es-discuss at mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131220/76ec2831/attachment.html>