Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

networkError payload should be an Error object #222

Merged
merged 1 commit into from
May 29, 2017
Merged

Conversation

scottinet
Copy link
Contributor

Description

The networkError event has an inconsistent payload: the main Kuzzle object may trigger it with an Error object (if unable to establish a connection), but the websocket wrapper triggers it with a string message if the socket gets unexpectedly closed.

@codecov-io
Copy link

Codecov Report

Merging #222 into 5.x will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##              5.x     #222   +/-   ##
=======================================
  Coverage   98.15%   98.15%           
=======================================
  Files          17       17           
  Lines        1953     1953           
  Branches      556      556           
=======================================
  Hits         1917     1917           
  Misses         36       36
Impacted Files Coverage Δ
src/networkWrapper/wrappers/websocket.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86d06b1...b93569e. Read the comment docs.

@scottinet scottinet merged commit 97b48ef into 5.x May 29, 2017
@scottinet scottinet deleted the networkError-payload branch May 29, 2017 14:31
@scottinet scottinet mentioned this pull request May 29, 2017
@scottinet scottinet mentioned this pull request Jun 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants