Update behavior for non-glob path strings #4
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
es128
force-pushed
the
non-glob-parent
branch
from
0713e7d
to
e083e5a
Compare
|
👍 on parity, I just skimmed the discussion |
es128
added a commit
that referenced
this pull request
Sep 18, 2015
Update behavior for non-glob path strings
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.
The discussion isn't necessarily settled yet, but just getting the PR started. When landed, should resolve #3.
As of now, this PR would provide parity with glob2base's treatment of regular (non-glob) paths.
/cc @jonschlinkert @robwierzbowski @contra @phated