Enable switching from/to DiffView based on 'merge' prop status #65
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
Switch from Editor mode to DiffView based on 'merge' prop status. History, value and cleanGeneration are preserved.
|
Update to v4.0.5 please. |
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.
Switch from Classic mode to DiffView (back and forth) based on 'merge' prop status. History, value and cleanGeneration are preserved.
User has to provide orig(Right) or origLeft and set 'merge' to true (has you would do in a statically initialized DiffView instance)
So far, 'merge' prop is only used at initialization and there is no watcher.
Idea came from the need in one of our project to examine patches while editing (thus switching from classic editor to merge view)