max-mapper / max-mapper/extract-zip
Extracting ZIPs sometimes makes subfolders and others dont
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 398
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
Depending on the zip file being extracted, it either makes a subdirectory with the name of the zip file as the folder and put its contents inside there or extracts the contents directly to targeted directory.
I want to control the behaviour across all extracted zips to be either extract everything in the targeted directory as it or make a subfolder of the named zip and push the zip content there. I cant seem to determine if there are optional parameters for this?
From observation, if the extracted zip has sub folders in it, it will then make a folder with the name of the zip and copy it all inside of it. Compared to a zip with no sub folders.
Are there any optional params to force one way of extracting?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the extract-zip API documentation and the current extraction behavior described in this issue. Determine whether the package exposes an option for choosing between a named subfolder and direct extraction, then verify the selected behavior against ZIPs with and without subfolders. Done means the behavior can be consistently selected across extracted archives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100