Releases: mradionov/karma-jasmine-diff-reporter
Releases · mradionov/karma-jasmine-diff-reporter
v3.0.0
Breaking changes
- Deprecating the plugin for Jasmine 4+. Will show a warning in karma output if trying to use with Jasmine 4+. More info in #63.
Chore
v2.0.1
Bugfixing
- Fixed use of
jasmine.matchersUtil.equals
(#50)
Chore
- Updated dependencies and dev dependencies to fix NPM audit errors and warnings
v2.0.0
Breaking changes
- Removed
legacy
option. Jasmine >= 2.6 will have built-in output overridden by reporter by default (#38)
Bugfixing
- Fixed output of empty objects and arrays (#36)
- Fixed Jasmine < 2.6 error by removing legacy flag (#39)
Chore
- Updated dependencies and dev dependencies. Added package-lock.json (#37)
- Droped support for node 4 and 5. Added support for node 10.
v1.2.1
Bugfixes:
- Fix for Jasmine 3.0 internal pretty printer
value.and.identity
type change. (#33)
v1.2.0
Feat:
- Support for setting a type of diff algorithm which will be used for custom matcher (#31)
v1.1.1
Docs:
- Updated README to adress Jasmine 2.6 built-in diffs and overriding Karma
plugins
option. (#29)
v1.1.0
Feat:
- Adds
legacy
option, which allows to bring back legacy Jasmine diff output and reporter diff highlight as well.
(#27)
Bugfixes:
- Removes highlight for Jasmine 2.6 toEqual diff. (#27)
v1.0.0
Breaking changes
- Removed
json
option. If you used this option to get rid of Object({ ... })
Jasmine wrapper, then you can use new option verbose: false
instead. (#17)
- Particular matchers now can't be configured to have different
pretty
and multiline
output. pretty
and multiline
are now the same for all matchers, configured in karma config file.
Bugfixes:
- Correct diffs for jasmine.objectContaining and jasmine.arrayContaining (#16)
- Highlight references with warning color (#18)
v0.6.3
Bugfixes:
- Reverts 0.6.2 and restores the behavior for highlighting
jasmine.objectContaining
(#16)
v0.6.2
Bugfixes:
- Do not diff with jasmine.objectContaining (#16)