The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of jest-enzyme.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes5.0.0
🛑Breaking
Removed toBePresent and toBeEmpty in favor of a new matcher toExist. (@blainekasten)
Improved error message when using an enzyme-matcher assertion with a non-enzyme argument. (@blainekasten)
Improve the message output from toHaveClassName. (@theneva)
toBeChecked previously failed on undefined or null values, but is now fixed. (@pascalduez)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 5.0.0 of jest-enzyme was just published.
The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of jest-enzyme.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
5.0.0toBePresent
andtoBeEmpty
in favor of a new matchertoExist
. (@blainekasten)jest-environment-enzyme
(@blainekasten)eslint-config-jest-enzyme
(@blainekasten)toBeEmptyRender
to assert when a component returnsnull
orundefined
. (@theneva)toHaveStyle
,toHaveProp
andtoHaveState
now all can accept an object as a list of key,values to match against. (@blainekasten)yarn
workspaces locally now. (@blainekasten)enzyme-matcher
assertion with a non-enzyme argument. (@blainekasten)toHaveClassName
. (@theneva)toBeChecked
previously failed on undefined or null values, but is now fixed. (@pascalduez)FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: