Renamed
upHasFailed
toupHasErrored
,downHasFailed
todownHasErrored
, andhasFailed
tohasErrored
and also introduced new functionhasFailed
.
template
and apply
were changed to process XHRs in parallel using the newly
added IdentityParallel
algebra, because that is what one more often wants.
Note that this doesn't change the behaviour of the IdentitySucceeded
algebra.
tap
added to perform side-effects and return the XHR
apply
was changed to accept both XHRs and plain values.
Fix work around for IE11 where 'progress'
events may be sent after 'load'
events.
Fixed bug in IE11 responseType
workaround.
Added work around for IE11 where 'progress'
events maybe be sent after
'load'
events.
Renamed
XHR.responseFull
toXHR.response
and dropped the old XHR.response
function, because getting the full response
is what one normally wants to do and having XHR.response
return partial
results seems unnecessarily error prone. The valid use cases of the old
XHR.response
can be implemented through XHR.responseText
.
Changed XHR.responseFull
to require that the download has completed
successfully.
Changed XHR.getJson
to wait that the XHR has completed successfully with a
HTTP success status and to emit the XHR as an error in case the XHR fails or
times out.
Renamed
XHR.downHasSucceeded
toXHR.downHasCompleted
, andXHR.upHasSucceeded
toXHR.upHasCompleted
to avoid them being confused with having the entire HTTP request being successful.
Also renamed
XHR.headersReceived
toXHR.isStatusAvailable
so that it sounds like a query.
Changed XHR.status
, XHR.statusText
, XHR.responseURL
, and XHR.responseXML
to wait for / require a meaningful ready state.
Fixed a bug introduced in 0.3.0 where observables were not properly eliminated
from perform
parameters in non-production mode.
performWith
now also merges default headers with override headers.
performJson
also includes header Content-Type: application/json
.
Previously allResponseHeaders
and responseHeader
produced ''
and null
,
respectively, before the HTTP headers were received. Now they only emit their
results after the HTTP headers have been received.
Previously responseXML
produced null
before the XHR was completed. Now it
only produces its result after the XHR has been completed like responseFull
.
Fixed a bug. Previously the XHR was aborted unconditionally after unsubscribing from the returned property. Aborting a completed XHR clears the XHR object, which we don't want as we want the XHR values to remain readable. Now the XHR is aborted only if the status is 0.