fix: Stop html encoding of options for generate-event #824
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
In mustache all variables ({{name}}) are HTML escaped, which is not what we want
for the generate-event command. To force unescaped HTML, you need to use the
triple mustache: {{{name}}}
willyg302
added a commit
to willyg302/aws-sam-cli
that referenced
this pull request
Aug 30, 2019
Everything switched to triple mustache in aws#824 except for these two occurrences.
6 tasks
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.
In mustache all variables ({{name}}) are HTML escaped, which is not what we want
for the generate-event command. To force unescaped HTML, you need to use the
triple mustache: {{{name}}}
Issue #, if available:
#755
Description of changes:
Checklist:
make prpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.