Make empty string a valid extension option #21
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 have a use case of gulp-swig where I use a
.swig
extension on the input files...something liketemplate.html.swig
. I would like gulp-swig to be able to just remove the extension entirely--i.e. use an empty string foropts.ext
. An empty string, however, is falsy, and so this pull request addresses my use case. The current behavior is mostly unchanged, as the default.html
extension is still applied ifopts.ext
isnull
orundefined
.