fix: unsafe read
usage with find
output
#86
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.
Description
Replaced a potentially unsafe use of
read
in awhile
loop fed byfind
. The previous version could misinterpret filenames containing spaces, tabs, or special characters. Updated it to usefind -print0
andread -r -d ''
for safe and reliable parsing. This is especially important when working with external file sources like git submodules or CI environments.How Has This Been Tested?
Tested locally with files containing spaces, tabs, and special characters in their names. Confirmed that all paths are correctly processed without breaking.
Checklist:
Before deployment
After deployment