Analyze all DragAndDrop files/folders before throwing exception(s) and aborting. #1
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
…d aborting. Default "checking" behavior throws exceptions upon encountering the first invalid checksum file and does not provide user with the path of the invalid checksum file in the exception message. Most users would prefer seeing a complete listing of all checksum files that need to be repaired/replaced in one drag and drop operation. New functionality traverses all files in the drag and drop selection before throwing a final exception containing a complete listing of bad checksum files.
|
Looks good, thank you. I'll pull down the change locally and check it out in the next few days. For anyone viewing this diff use |
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.
Default "checking" behavior throws exceptions upon encountering the
first invalid checksum file and does not provide user with the path of
the invalid checksum file in the exception message. Most users would
prefer seeing a complete listing of all checksum files that need to be
repaired/replaced in one drag and drop operation. New functionality
traverses all files in the drag and drop selection before throwing a
final exception containing a complete listing of bad checksum files.