Prior to Jasmine 3.6, matchers that wanted to support custom equality testers had to accept them as an argument to the matcher factory and pass them to MatchersUtil#equals and MatchersUtil#contains. That's not required beginning with 3.6. It'll produce a deprecation warning in 3.99 and fail in 4.0. This PR updates jasmine-enzyme to be compatible with the planned changes in Jasmine 3.99 and 4.0, while maintaining compatibility with older versions.
I've tested this by running a usage of toHaveState that relies on custom equality testers against the following versions of the jasmine package:
3.5.0github:jasmine/jasmine-npm#3.99github:jasmine/jasmine-npm#4.0
Prior to Jasmine 3.6, matchers that wanted to support custom equality testers had to accept them as an argument to the matcher factory and pass them to MatchersUtil#equals and MatchersUtil#contains. That's not required beginning with 3.6. It'll produce a deprecation warning in 3.99 and fail in 4.0. This PR updates jasmine-enzyme to be compatible with the planned changes in Jasmine 3.99 and 4.0, while maintaining compatibility with older versions.
Additional context: https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#matchers-cet
I've tested this by running a usage of toHaveState that relies on custom equality testers against the following versions of the
jasminepackage:3.5.0github:jasmine/jasmine-npm#3.99github:jasmine/jasmine-npm#4.0