Previously, this was treated as if the maxEditLength option wasn't provided at all, which seems surprising. Obviously, passing maxEditLength: 0 isn't usually gonna be a very useful thing to do, but you can imagine a system where there's a configurable max edit distance between two texts with a UI that lets you put it all the way down to 0, and jsdiff is being used both to check that the max distance is being adhered to and to display the diff. In such a case, the current behaviour would introduce a surprising bug in the maxEditLength: 0 case.
This PR makes jsdiff instead treat maxEditLength: 0 as specifying a max edit length of 0.
Previously, this was treated as if the
maxEditLengthoption wasn't provided at all, which seems surprising. Obviously, passingmaxEditLength: 0isn't usually gonna be a very useful thing to do, but you can imagine a system where there's a configurable max edit distance between two texts with a UI that lets you put it all the way down to 0, and jsdiff is being used both to check that the max distance is being adhered to and to display the diff. In such a case, the current behaviour would introduce a surprising bug in themaxEditLength: 0case.This PR makes jsdiff instead treat
maxEditLength: 0as specifying a max edit length of 0.