Fix oversight where Scanner.cs won't scan for files if an archive extracts to one or more directories #397
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HeroponRikiBestest
changed the title
mnadareski
reviewed
Nov 29, 2025
mnadareski
approved these changes
Nov 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, scanner.cs determines whether scanning needs to be done to any files extracted from an archive by checking
IOExtensions.SafeGetFiles(tempPath).Length > 0on the extracted path. Some archives extract to one or more top-level directories that contain files within themselves, resulting in nothing being scanned. This PR checks the number of directories too. Unsure if you'd want to have some sort of logic to check if the directories are empty or not.Example archive, if needed (unrar.7z):
unrar.7z.zip