Properly encode entities when serializing XML #150
Merged
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
drewish
force-pushed
the
entity-encoding
branch
2 times, most recently
from
037c9df to
1582923
Compare
drewish
force-pushed
the
entity-encoding
branch
from
1582923 to
3c347a6
Compare
This was referenced Apr 13, 2015
|
Looks good 👍 |
bhelx
added a commit
that referenced
this pull request
Apr 13, 2015
Properly encode entities when serializing XML
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.
Fixes #148. This also syncs up the style for creating the
$attribute_nodein thenullcase.