Add handlers for websocket connection error and closed #3410
Conversation
This file contains 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
Signed-off-by: Ann Shumilova <[email protected]>
akurinnoy
approved these changes
Dec 16, 2016
olexii4
approved these changes
Dec 16, 2016
|
Build # 1343 - FAILED Please check console output at https://ci.codenvycorp.com/job/che-pullrequests-build/1343/ to view the results. |
benoitf
approved these changes
Dec 16, 2016
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.
What does this PR do?
Adds ability to register handlers for websocket connection closed and error events. On workspace creation page, where statuses are tracked, the notification popup will appear if websocket connection closes during status tracking.
What issues does this PR fix or reference?
#3109
Signed-off-by: Ann Shumilova [email protected]