Skip to content

Releases: yahoo/fetchr

Re-throw an error for rejecting Promise

13 May 20:14
Compare
Choose a tag to compare
v0.5.29

Release v0.5.29.

Fix inconsistent error objects on client and server

13 May 20:14
Compare
Choose a tag to compare

Fix inconsistent error object and refactor tests

05 May 21:02
Compare
Choose a tag to compare

[#143] - Refactor tests and fix inconsistent error object output

Bug Fix

05 May 20:02
Compare
Choose a tag to compare

[#140 ] Use 500 as default status code for errors, instead of 400

Security fix for legacy browser

14 Jan 00:29
Compare
Choose a tag to compare

Bugfix: Allow metadata for erroneous responses

11 Jan 18:47
Compare
Choose a tag to compare

Up till version 0.5.17 erroneous responses were able to carry meta-data but this feature was lost when we changed the fetchr interface to support promises.

#130 - Allow metadata/headers for erroneous responses. Thanks @banghui.

Add responseFormatter support

04 Dec 00:05
Compare
Choose a tag to compare
v0.5.22

Release v0.5.22.

Bugfix: Don't serialize undefined values

02 Dec 02:04
Compare
Choose a tag to compare

Fix #55 via #132. In the past undefined values were being sent to the server where they were being parsed as the string "undefined". Instead, we now don't even send the value if it is undefined. Thanks to @AaronLasseigne.

Chain promise to avoid bluebird's "Unhandled rejection" error

01 Oct 18:36
Compare
Choose a tag to compare

Remove extra request execution

26 Sep 04:03
Compare
Choose a tag to compare

#124 - Remove extra request execution generated from 0.5.18