WIP: Fix definition of success in newXMLHttpRequestWithError #415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here the sample code demonstrates this change:
Before this change, press the button to cause Xhr error and you got:
After this change, press the button to cause Xhr error and you got:
It's great that
performRequestAsyncWithError
stops returningRight 0
on error and reports exception correctly. But nowperformRequestAsync
andgetAndDecode
become silent, which would need some discussion.In the case of
performRequestAsync
, it's appropriate to keep silence on error since it returnEvent t XhrResponse
and we won't get one on the error case.For
getAndDecode
which createsEvent t (Maybe a)
, should we map Xhr error toNothing
or not emitting this event?