Allow Relative Paths #69
Open
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
passing `relative === true` will prevent the finally output file from being coerced to an absolute path.
#5b03620
|
Sorry for the extremely long wait here. How does this play in with #67 ? |
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.
This pull request adds an option to pass
{ relative:true }to the path object (either through the object or function methods) in order to keep the path relative to the file glob. Normally this bit is removed and renamed withgulp.dest()but when renaming and concatenating compiled JST template files, the full absolute path name is passed making the name of the template non-portable if developers set up their build environments in different locations.This small change allows users to pass a flag that eliminates the step of re-applying the absolute path and allows the path to remain relative.