-
Notifications
You must be signed in to change notification settings - Fork 28
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
Path::Class::Dir->contains doesn't handle ".." #43
Comments
I'm assuming you meant two dots instead of three dots in the example? |
yes :-) Also to reproduce the test there needs to be a subdirectory named "lib". |
I added a fix & tests for this, want to take a look? |
The changes made in 935eeed introduces a regression (confirmed with git bisect) Starting with that commit, the following cmdline prints mkdir -p deleteme/test/path
touch deleteme/test/path/somefile
perl -Ilib -e '
use Path::Class "dir", "file";
dir("deleteme/test/../test/path/")
->contains(file("deleteme/test/../test/path/somefile"))
or print "FAIL!!\n"
' This change is breaking some of the auto-generated dev scripts for RapidApp users, which are already out in the wild, so the sooner this can be fixed (broken in v0.36 on CPAN) the better. Thanks |
Need to resolve both $self and $other before comparing them with subsumes.
Need to resolve both $self and $other before comparing them with subsumes.
Need to resolve both $self and $other before comparing them with subsumes.
Sorry for not following up sooner. My issue was resolved, but I found the problem affecting vanstyn, and went ahead and fixed them in pull request #48. |
Now that #48 is merged, is this issue resolved to everyone's satisfaction? |
Yes! Can we ship to CPAN quickly?? |
Sure. Will do now. |
Thank you!!! |
No problem, thanks for reaching out to get it fixed. |
The documentation for contains says that it checks the filesystem to see if one directory is contained within another, however
shows that it didn't actually resolve the directories or even logically deal with the "..".
The text was updated successfully, but these errors were encountered: