Fix for decoding part of issue #74 #89
Open
Conversation
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
|
Do you have tests that verify the new decoding code? |
|
Good point, I'll try to construct one |
|
FIY, you could add them to the https://github.com/jmesnil/stomp-websocket/blob/master/browsertests/unit/frame.js tests which deals with encoding/decoding of STOMP frames. Thanks! |
|
I changed one character in the message.js test, which generated an error before my fix. When the fix is applied, the test passes. |
|
I put the unicode test in a separate unit test and added more unicode characters to the fixture. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Messages containing UTF8 is being decoded by using the functionality found in http://snipplr.com/view.php?codeview&id=31206