You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**What's the problem this PR addresses?**
The `ZipFS` implementation doesn't support the `recursive` flag.
Fixes part of #5423
**How did you fix it?**
I implemented the `recursive` flag and updated the types to account for
it. However I didn't make `ZipOpenFS` automatically traverse through zip
archives ... My line of thinking was:
> - on one hand, tools implementing their own readdir-based recursive
traversal don't currently dig into zip archives
> - on the other hand, it can be argued that the other recursive Node.js
native operations also apply to the zip archives' content (`cp` / `rm`)
>
> But I tend to think the first point is more important ... I feel like
the recursive flag should just be an optimization, so it should have the
same behaviour as a manual traversal ...
**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.
<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.
0 commit comments