ConnectionEventListener null safety issue #5
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
As seen here https://github.com/pusher/pusher-websocket-java/blob/master/src/main/java/com/pusher/client/connection/ConnectionEventListener.java code and exception can be null.
|
I'll include this in the next minor release |
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.
As seen here https://github.com/pusher/pusher-websocket-java/blob/master/src/main/java/com/pusher/client/connection/ConnectionEventListener.java
code and exception can be null.
This can be tested if while connected to pusher you close your internet connection. The error from the underlying websocket library has a null exception and code.