Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(valid-expect): support asyncMatchers option and default to jest-extended matchers #1018

Merged
merged 1 commit into from
Jan 15, 2022

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Jan 1, 2022

Have made the default the matchers from jest-extended, as I that's a pretty reasonable thing to do.

Fixes #488

@G-Rath G-Rath force-pushed the support-jest-extended-matchers branch from 6db4cbc to 00234f8 Compare January 14, 2022 19:00
@G-Rath G-Rath merged commit c82205a into main Jan 15, 2022
@G-Rath G-Rath deleted the support-jest-extended-matchers branch January 15, 2022 20:39
github-actions bot pushed a commit that referenced this pull request Jan 15, 2022
# [25.7.0](v25.6.0...v25.7.0) (2022-01-15)

### Features

* create `prefer-equality-matcher` rule ([#1016](#1016)) ([341353b](341353b))
* **valid-expect:** support `asyncMatchers` option and default to `jest-extended` matchers ([#1018](#1018)) ([c82205a](c82205a))
@github-actions
Copy link

🎉 This PR is included in version 25.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[valid-expect]: support specifying custom async matchers
1 participant