Implemented escaping mechanism #75
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
spookylukey
force-pushed
the
implement_escapers
branch
from
c1e34b5 to
66cf690
Compare
spookylukey
force-pushed
the
implement_escapers
branch
from
e208977 to
c379fb6
Compare
|
Closing this for now, will re-visit later |
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.
This adds a mechanism to handle escaped text (e.g. HTML escaping). The test includes an example that works with markupsafe, and in django-ftl I'm using the same mechanism to work with HTML in Django templates.
This should be reviewed after #67 and #71 since it builds on them.