Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Always use posix paths in asset generation #1354

Merged
merged 2 commits into from
Mar 29, 2017
Merged

Always use posix paths in asset generation #1354

merged 2 commits into from
Mar 29, 2017
+23 −17

Commits on Mar 29, 2017

  1. Always use posix paths in asset generation 

    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.
    @chuckries
    chuckries committed Mar 29, 2017
    Configuration menu
    Copy the full SHA
    9292f7c View commit details
    Browse the repository at this point in the history

  2. Update changelog

    @chuckries
    chuckries committed Mar 29, 2017
    Configuration menu
    Copy the full SHA
    d3ba536 View commit details
    Browse the repository at this point in the history