Skip to content

Releases: sudhirj/simply-deferred

v3.1.0

30 Sep 13:20
Compare
Choose a tag to compare

Arrays were being flattened when being used as resolution values - fixed thanks to @antialias

v3.0.0 - Full jQuery compatibility

05 Jan 18:44
Compare
Choose a tag to compare

Thanks to @lkwdwrd Simply Deferred is now fully compatible with jQuery - including progress callbacks.

Also thanks to @ericmatthys for bugfixes.

v2.4: AMD compatibility and `pipe` fixes

17 Oct 06:09
Compare
Choose a tag to compare

Thanks to @smcmurray for providing AMD compatibility.

Thanks to @rraval for a new pipe implementation that is more compatible with the jQuery edge cases.

This release may break code that uses pipe and relies on wrong (jQuery-deviant) behaviour.

v2.3: Changes in `[resolve|reject]With`

04 Aug 13:51
Compare
Choose a tag to compare

As @fukamachi pointed out in #15, there were two problems with the resolveWith and rejectWith API that were deviant from jQuery:

  • both methods now return the deferred they were called on to enable chaining.
  • both now accept a context as the first argument and an array as the second. The elements of the array are passed as arguments to the callbacks. Earlier, any objects could be passed and they would be sent to the callback as an array.

Bumping to 2.3 because this will break existing code that relies on the faulty API.

v.2.2

27 Jul 10:54
Compare
Choose a tag to compare

This releases primarily changes the when() method, adding the following improvements:

  • when() now supports calling it with no arguments
  • .promise() can be called on promises
  • $.when() can handle non-deferred arguments, and treats them as pre-resolved deferreds. This turns out making $.when(...) with all resolved arguments a shorthand for $.Deferred().resolve(...).promise(). jQuery treats every object that implements a .promise() function as a deferred. This has special implications for .pipe().

Most of the work for this release was done by @rraval via #14 - so a big thank you goes there.

Bumping to 2.2 because this may break code that relies on these features not being present.

v2.1.0

10 Jul 12:22
Compare
Choose a tag to compare

As described by the docs, the then method now provides special treatment to filters which return deferreds. Where previously they were passed on like any other value, they're now resolved / rejected based on the context. Fixes #12.

Bumping to 2.1.0 because this make break compatibility with existing code that relies on this behaviour not being present.

v2.0.0

10 Jul 12:10
Compare
Choose a tag to compare

Adds major compatibility fixes that may break older versions.