vfs: support renaming implicit ZIP directories - #65752
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #65752 +/- ##
==========================================
- Coverage 92.40% 90.19% -2.22%
==========================================
Files 417 771 +354
Lines 188989 265493 +76504
Branches 28924 50457 +21533
==========================================
+ Hits 174642 239449 +64807
- Misses 14015 16987 +2972
- Partials 332 9057 +8725
🚀 New features to boost your workflow:
|
|
@pipobscure ... just want to get your review on this as well. |
This comment was marked as outdated.
This comment was marked as outdated.
|
LGTM definitely a step in the right direction. Made me think of another edgecase where the provider could be better in a write/rename situation. |
|
In this context, we (probably I) should also take a look at #65373 to make sure the bahaviour is fully correct for ZipArchives. Decision Needed: merge this and then fix the issues as this is already a significant improvement, or fix the latent rename issues in one go. My €0.02 is to merge and continue improving, that's after all what --experimental is for. |
1bb560a to
8e7df26
Compare
|
Re-requested a review from @jasnell as a regression test was added based on feedback in #65752 (comment) |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Treat archive entry prefixes as directories when renaming with ZipProvider. Move all descendant entries to the new prefix for both asynchronous and synchronous operations. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> Assisted-by: codex:gpt-5.6-sol
8e7df26 to
5263f98
Compare
Fixes: #65751
Treat archive entry prefixes as directories when renaming with ZipProvider. Move all descendant entries to the new prefix for both asynchronous and synchronous operations.
Assisted-by: codex:gpt-5.6-sol