WIP: Fix definition of success in newXMLHttpRequestWithError#415
Open
TheKK wants to merge 1 commit intoreflex-frp:developfrom
Open
WIP: Fix definition of success in newXMLHttpRequestWithError#415TheKK wants to merge 1 commit intoreflex-frp:developfrom
TheKK wants to merge 1 commit intoreflex-frp:developfrom
Conversation
When ready state is DONE (4), we also needs to check its status to know if it is success or not. According to MDN [1]: Before the request completes, the value of status is 0. Browsers also report a status of 0 in case of XMLHttpRequest errors. [1]: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/status
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
performRequestAsyncWithErrorstops returningRight 0on error and reports exception correctly. But nowperformRequestAsyncandgetAndDecodebecome silent, which would need some discussion.In the case of
performRequestAsync, it's appropriate to keep silence on error since it returnEvent t XhrResponseand we won't get one on the error case.For
getAndDecodewhich createsEvent t (Maybe a), should we map Xhr error toNothingor not emitting this event?