Fix FileUtils on macOS #1863
Merged
Fix FileUtils on macOS #1863
Conversation
This file contains 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
smilediver
changed the title
FileUtils::getFileSize() and FileUtils::fullPathForDirectory()
rh101
reviewed
Apr 29, 2024
smilediver
changed the title
|
Added two more fixes:
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes the following issues that
unit-testshave exposed on macOS.FileUtils::getFileSize()returning 0 instead of -1 when file is not foundFileUtils::fullPathForDirectory()not returning path with a trailing slashFileUtils::getDefaultResourceRootPath()returning empty string on macOSFileUtils::isFileExist()returning true for directories on macOS