Future 6.0.0 release #446
Merged
Future 6.0.0 release #446
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
…th unified diffs (#435) * Add test of vertical tab handling * Stop treating stuff like vertical tabs as line breaks when dealing with unified diffs * Add release notes * Add a consistency test
… same, like the Myers diff paper does (#439) * Add test for Unix diff-style ordering of deletions & insertions * Tweak base.js to prefer extending paths that have previously done more deletions * Remove now-redundant code to flip the order of immediately consecutive add and remove operations * Fix existing tests * add release notes
|
Is there a pre-release available of this? |
|
@adaboese you can just clone the repo, switch to this branch, and install it with |
Conflicts: README.md
…ay you'd expect (#464) * Add failing test showing maxEditLength: 0 is handled wrongly * Handle maxEditLength === 0 correctly (test now passes) * Document change
* Add a oneChangePerToken option to emit one change object per token instead of combining consecutive tokens into one change object * Document oneChangePerToken * Add release notes * Add test (which fails; needs changes from #439) * Add test of case with identical texts * Add another test * Move release notes to correct place now that I'm planning this for 6.0.0
* Ensure the left & right arguments to equals() always correspond to old and new values respectively * Add test * Add release notes
Conflicts: test/diff/array.js
* Add test demonstrating that maxEditLength crashes createPatch * Fix maxEditLength handling in createPatch * Add release notes
Conflicts: release-notes.md
|
Now that 5.2.0 is released, I'm going to merge this PR into |
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.
Just a PR to keep track of the future 6.0.0 release. I'm currently merging non-breaking changes into master (for a 5.1.1 or 5.2.0 release) and breaking ones into 6.0.0-staging (for a subsequent release after that).