New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Suggestions for Decompressing Callback Logic #162
Comments
Not since the v4.0.0-rc, where the callback provides the full path of the file within the archive, not just its file name.
The problem is that directories are not actually "extracted"; when bit7z encounters a directory item, it simply recreates it in the output folder.
I'm evaluating whether to provide a Another option would be adding a new "item" callback, which should also report directories.
Returning the decompression path would make the API less easy to use for users not interested in manipulating such information. Thanks for the suggestions! |
Feature description
During the decompression process, the situation: when the setFileCallback is triggered during the decompression process, only the file name (without directory information) is provided and no callback is made when decompressing the directory. The return value of the Callback is only whether the current file needs to be decompressed.
Suggestion: When triggering the setFileCallback setting function during the decompression process, the item of the directory and the file should be used as the Callback parameter. In this way, the developer can display more comprehensive information to the user, allowing the user to choose how to operate; in the return of the Callback function In addition to whether to decompress the current file, the value should also provide the decompression path, so that the developer has more room for manipulation when the user chooses to overwrite or rename
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: