This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Fix display of JSON-format string message bodies #31
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
UTF-8 encoded strings that could be parsed as JSON were being shown in the output as an empty pair of braces {} because the actual global JSON object itself was being printed, not the body of the message.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Checklist
Reference/Link to the issue solved with this PR (if any)
Description of the problem
Message bodies that could be parsed as UTF-8 encoded JSON strings were being shown in the output as an empty pair of braces {} because the actual global JSON object itself was being printed, not the body of the message.
Description of the solution
Correct the call to JSON.stringify() that was probably only missing due to a typo.