fix: Fix missing leading slash causing extra getDirectoryContents entries #324
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
Merged
|
For some reason the tests won't run on PRs from forks, so I had to merge this to a temporary branch to run them. |
|
Worked! Thanks @Cobertos for this fix.. Much appreciated 🙏 |
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.
If you don't have a leading slash passed to
getDirectoryContents, it will cause it to not properly filter out the current directory from the response. This PR fixes that.This is the actual cause of the issue I was having in the
webdav-fsrepo. perry-mitchell/webdav-fs#84