Singular file zipping vs multiple file zipping

Hi there i noticed a very small inconsistency with the zipping of a given directory, I noticed that if you zip a directory with a singular file, there is no inner folder in the given zip. Whereas if you have multiple files in a directory the files in a directory are wrapped by an overall folder, with the original folders name. So as an example:

Directory (Single File):

├───DirectoryBeingZippedWIthSingleFIles
│   ├───test.txt

If you were to unzip the generated zip for the above, it gives you just the file i.e test.txt.

Directory (Multiple Files):

├───DirectoryBeingZippedWithMultipleFiles
│   ├───test.txt
│   ├───test.txt

If you were to unzip the generated zip for the above, it gives you the files but wrapped in a folder called DirectoryBeingZippedWithMultipleFiles

Proposed Solution

So the idea, which i have implemented locally, is to allow a option to be passed into the set of options, which allows you to specify the inner folder name, and as such be able to provide a name for when there is only a singular file.

This was a small issue in a project where we had to do some zipping and unzipping of directories, where the output format was not consistent when the directory sizes were not consistent. And as mentioned, i have implemented this locally, but raising issue for further discussion. :)

The issue names no files or tests. Start by locating the directory-zipping entry point and reproduce the single-file and multiple-file examples; done means an option can consistently provide the intended inner folder name for both cases.