Use JSON.dump instead of to_json #10
Closed
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
In newer Rails 3.2 and above, to_json will convert HTML characters into unicode entities. SparkPost will choke when creating a transmission with inlined HTML SimpleSpark should use JSON.dump instead to so that HTML entities aren't escaped.
Contributor
|
Going to go with similar request #11 Using JSON.generate as it calls dump internally but allows additional options, nice catch thanks |
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.
In newer Rails 3.2 and above, to_json will convert HTML characters into
unicode entities. SparkPost will choke when creating a transmission
with inlined HTML SimpleSpark should use JSON.dump instead to so that
HTML entities aren't escaped.