This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
Support for implicity array and overriding encoding options #17
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
…erride the default behavior of encoding
* Added unit tests for overrides & implicit iterators
…an process on the raw value (instead of the encoded value)
dswitzer
added a commit
that referenced
this pull request
Aug 22, 2012
Support for implicity array and overriding encoding options
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.
I actually did this work a while back, but I'm just now getting back to this code. I've implemented a couple of patches I thought worthy of migrating back into the source:
{{#array}} array value: {{.}} {{/array}}{{ }}and{{{ }}}evaluated text. I did this so someone has the ability to overwrite the behavior of{{...}}and{{{...}}}. For our use case, we need to explicit handle how text is rendered based upon how it's being used in the code (we're using Mustache to give our users some templating processing abilities for e-mail generation.) So if we're rendering an HTML e-mail, we always want to html encode the text and likewise for text e-mails we always want to render the text as-is.