Remove matchers already existing in Jest 25?

[thernstig]

This is more of a discussion than a bug or feature request.

I noticed that jest-extended contains some matchers that already exist in the latest Jest. Example: toContainKey === toHaveProperty

Would there be an idea to remove these matchers? It is confusing for developers of a project the more matchers there exist, due to recognizability.

Or did I misunderstand toContainKey vs toHaveProperty?

[keeganwitt]

They don't use the same mechanism, but they seem to be able to provide the same functionality.

This would require bumping up the minimum required version of Jest before that'd be possible though.