Always use posix paths in asset generation #1354
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
We were using native 'path.join' when creating paths for VS Code assets (tasks.json, launch.json). On windows this would produce windows style paths. If the assets are checked into source control and used on posix systems, they will break. Posix paths will run perfectly fine on windows, so always use posix paths.
|
Fixes #1351 |
gregg-miskelly
approved these changes
Mar 29, 2017
|
Feel free to update the change log if you like. |
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.
We were using native 'path.join' when creating paths for VS Code assets
(tasks.json, launch.json). On windows this would produce windows style
paths. If the assets are checked into source control and used on posix
systems, they will break. Posix paths will run perfectly fine on
windows, so always use posix paths.