This repository has been archived by the owner on Jan 12, 2022. It is now read-only.
fix keywords being escaped #29
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
|
Looks like |
|
Ack! Thanks for finding and taking care of these bugs, I've been a bit distracted. |
|
No worries, we're all busy! Also I will take the blame for this since I suggested moving to full mustache 😉 |
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 was getting explosions when adding keywords. The
package.jsonhad this in it:So, it looks like
mustacheis escaping characters by default. This must be different behavior thanmicromustache.This PR fixes it by adding another set of 'staches around pkgKeywords in
package.json.mustache.