Modified setOutputPath to correctly handle extensions. #6
Conversation
This file contains hidden or 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
| if (extension) | ||
| output = output.replace(path.extname(output), '.'+extension) | ||
|
|
||
| file = new File(this.conf.output.path, output) |
Member
There was a problem hiding this comment.
Make sure to run npm lint to check for lint errors, there are few in here like multi-line if/for statements without brackets
Author
|
I fixed the linter problems (sorry about that), but I'm unfamiliar with coveralls/your test suit. |
Member
|
Thank you! If it helps at all, this is our contributing guide 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Modified setOutputPath as we discussed in Gitter.