This repository has been archived by the owner on Mar 18, 2022. It is now read-only.
Add ability to specify template extension #31
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
|
nice work jake! |
niftylettuce
added a commit
that referenced
this pull request
Jan 1, 2013
Add ability to specify template extension
|
i have to go through a few other pull requests, issues, and adding contributors to credits in Readme/package.json before I can push to NPM v0.1.0! we've come a long way! |
|
Why this commit is not in the master if it was merge? |
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.
Currently when in production mode, only .ejs and .jade templates are scanned for CDN() usage. I'm using swig templates. These files have a '.html' extension.
This pull requests adds the ability to specify 'extensions' via the options when different than the default.