feat(compare): explain how each file differs from its counterpart - #112
Merged
Merged
Conversation
…ff notice to only appear on selected line
DPassarelli
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The change list now explains how each differing file compares with the copy it would replace. The row under the cursor reports the size gap between the two copies and how long ago each was last written, so you can tell whether the incoming file is the one you were just working on or something stale about to overwrite newer work. A file whose size and timestamp both match, yet whose contents differ, is named as such, since that is the state most easily mistaken for a bug. Previously a row said only that a file differed, leaving the reason and the direction to guess.
Closes #72