Properly escape sharedPath in generated import statements#229
Merged
Rich-Harris merged 1 commit intosveltejs:masterfrom Jan 3, 2017
Conduitry:escape-shared-path
Merged
Properly escape sharedPath in generated import statements#229Rich-Harris merged 1 commit intosveltejs:masterfrom Conduitry:escape-shared-path
Rich-Harris merged 1 commit intosveltejs:masterfrom
Conduitry:escape-shared-path
Conversation
|
+1 |
1 similar comment
|
+1 |
Member
|
thank you! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
If the
sharedPathcontains any special characters, the generatedimportstatement is not correctly escaping them. This PR fixes that.As an added bonus, unit tests pass on Windows again. Previously, the unit tests which used
sharedwere generatingwhich is the same as
'C:somepathsvelteshared.js', which reify rightfully balked at.