Enzyme Matchers Versions Save

• toContainMatchingElement and toContainMatchingElements now can take a list of Enzyme wrappers. (@GreenGremlin)
• Improved messaging for toContainMatchingElement and toContainMatchingElements. (@GreenGremlin)

• Update a security advisory within dependencies. (@tgaff)
• Various package improvements. (@goldensunliu, @mulholio, @kahwee, @tgaff)
• Fixing messaging for toHaveState and toHaveProp. (@GreenGremlin)

• Fix a jest integration with toContainMatchingElement not returning an explicit boolean. (@blainekasten)

• Fix duplicate typescript definition. (@GreenGremelin)

🛑 Breaking

• Renamed toHaveTagName to toHaveDisplayName (GreenGremlin)
  • This was done because Tag name indicates an HTML entity, but the matcher works with React Components which uses an internalProp displayName
  • When updating to 7.0.0 you should be able to just do a simple search and replace for this matcher across your codebase.

🍾 Improvements

• Add support for unboxed properties for toMatchElement. (@blainekasten)
• Improve documentation for the entire repo. (@blainekasten)
• Improve internal tests.

Failed Release

• Added 3 new matchers! toContainMatchingElement, toContainMatchingElements and toContainMatchingElements (@GreenGremlin)

• Fix typescript definitions for toMatchElement options argument. (@mayhewluke)

• Fix global typescript definitions for jest-environment-enzyme. (@vkrol)

• Add global typescript definitions for jest-environment-enzyme. (@astorije)
• Allow multiline strings for toHaveHTML. (@astorije)
• Print local error messages when jest-environment-enzyme has an issue. (@h.ayabe)