Fix erroneous error message on browser ws error #463
Merged
+24
−2
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.
Description
The
onerror
event handler called in browsers' WebSocket API differ from the one exposed by thews
module used in Node.js: the handler in browsers receive a genericEvent
object without any error information, while the ws handler receives a proper error.Result:
kuzzle.connect().catch(e => console.log(e))
prints something likeError: [object Event]
in a browser's console.This PR fixes that issue by detecting the case and sending a generic
Connection error
to the connect promise handler.How to reproduce
Run the following script in a browser:
Without this PR, the console should show the following message:
Error: [object Event]
With this PR:
Error: Connection error