-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fix the cwd
option
#96
Conversation
I don't think that's necessary. Each test gets their own unique temp directory: https://github.com/sindresorhus/del/pull/96/files#diff-1dd241c4cd3fd1dd89c570cee98b79ddR31 |
Two tests fail without the change, I think that is because of the I am inclined to think we should remove option Should I:
|
The tests doing |
They could, but if the check is broken it will actually remove files inside the project. I think using |
I am unsure how to properly solve the branch conflicts without using force push. Do I use merge or rebase? |
Ok, let's just use |
Sorry, I should have been clearer. I just meant don't use amend or squash and then force push. It's totally fine to resolve conflicts and then force push. |
Understood! I force pushed to solve the merge conflicts without any other changes. BTW, I have an additional PR almost ready so you might want to hold off on publishing a new release if you were planning on it. |
I was planning to do that, so thanks for letting me know. I will wait then. |
cwd
option
Currently when using
cwd
outside ofprocess.cwd()
thesafeCheck
works differently for relative and absolute file patterns. Absolute file paths will fail thesafeCheck
, but relative file paths will pass. This PR fixes so all file paths are treated the same and are relative to thecwd
option.I also added several tests and made them all run serial because so they can properly cleanup the temp directory between tests.