-
-
Notifications
You must be signed in to change notification settings - Fork 156
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.
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
base option possibly not reflecting correct default value #129
Comments
You are specifying absolute paths. All paths are resolved using node's |
I understand the unix convention and node's path resolution semantics but that wasn't my question. My question is: what is considered "not a glob"? And depending on that answer, why is the |
Anything that doesn't have glob magic is "not a glob". The |
So:
Means that |
No, it gets resolved |
…s for default base option values.
#129 - Update documentation to more clearly explain what happens for default base option values.
#129 - Update documentation to more clearly explain what happens for default base option values.
Forgive me if I'm not understanding something correctly here. In the
base
option, you say:This I think I understand correctly in that if you specify
something/**
thatbase
will besomething
and**
will be the glob.However, you also say:
What is considered "not a glob"? Is this something that doesn't contain a pattern? An empty string? A relative path? An absolute path?
If an absolute path classifies as a non-glob argument, then if you do something like:
Then the
base
is automatically set as/file
instead of whatever the current working directory is. That said, I can kind of see the point of this because if you had two completely separate globs that the base path would be ambiguous. But then why have it default at all? The only way a base path could be unambiguous would be if you passed a string glob instead of an array.In order to get around this you can force the
base
option via the second argument but I'm still wondering if this is the correct behaviour.The text was updated successfully, but these errors were encountered: