fix: fix directory traversal#136
Merged
Merged
Conversation
Coverage Report for CI Build 29183110144Coverage remained the same at 100.0%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
This was referenced Jul 12, 2026
12 tasks
The legacy Entry API (readEntries) throws on some platforms, e.g. dragging a folder from Windows Explorer into Chromium, which rejected the entire drop. Prefer getAsFileSystemHandle for directories and fall back to readEntries. Closes #130
rolandjitsu
force-pushed
the
fix/fsa-traversal
branch
from
July 12, 2026 06:44
c1114a3 to
1947f7c
Compare
|
🎉 This PR is included in version 3.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Fix #130.
Does this PR introduce a breaking change?
No.
Other information
Stacked on top of #133 and #135.