Skip to content

fix(zip): allow set folder date for fix #590 - #610

Merged
jonkoops merged 2 commits into
Stuk:mainfrom
bluelovers:issues-609
Sep 9, 2026
Merged

jonkoops merged 2 commits into
Stuk:mainfrom
bluelovers:issues-609

Conversation

@bluelovers

@bluelovers bluelovers commented Jul 25, 2019 •

Copy link
Copy Markdown
Contributor

fix #590

bluelovers and others added 2 commits September 9, 2026 11:34
Remove the public folder() options API from the community fix; folder
date inheritance belongs in the internal fileAdd to folderAdd path only.

Add tests that auto-created folders share explicit and unstamped file
dates on nested paths, and a test helper to make separate unstamped
new Date() calls observable.

Signed-off-by: Jon Koops <jonkoops@gmail.com>
@jonkoops jonkoops changed the title fix(zip): allow set folder date for fix #609 fix(zip): pass file date to auto-created parent folders Sep 9, 2026
@jonkoops jonkoops changed the title fix(zip): pass file date to auto-created parent folders fix(zip): allow set folder date for fix #590 Sep 9, 2026

@jonkoops jonkoops left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @bluelovers for the original fix. I narrowed the change to the bugfix only (pass o.date through folderAdd when file() auto-creates parents) and dropped the public folder() options API, since that would be a new feature rather than part of this fix. Added regression tests for explicit and unstamped dates on nested paths. Updated the linked issue to #590, which is what this actually fixes.

We will leave #609 open for a more comprehensive fix. The folder() options work is a good API addition and we can land that separately.

@jonkoops
jonkoops merged commit 0e2ea24 into Stuk:main Sep 9, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Different md5 for the same archive

2 participants