Skip to content

Conversation

@G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Oct 4, 2021

Fixes #921

@G-Rath G-Rath merged commit 99b6d42 into main Oct 4, 2021
@G-Rath G-Rath deleted the prefer-to-be-no-regexp branch October 4, 2021 04:07
github-actions bot pushed a commit that referenced this pull request Oct 4, 2021
## [24.5.1](v24.5.0...v24.5.1) (2021-10-04)

### Bug Fixes

* **prefer-to-be:** don't consider RegExp literals as `toBe`-able ([#922](#922)) ([99b6d42](99b6d42))
@github-actions
Copy link

github-actions bot commented Oct 4, 2021

🎉 This PR is included in version 24.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this pull request Oct 10, 2021
# [25.0.0-next.6](v25.0.0-next.5...v25.0.0-next.6) (2021-10-10)

### Bug Fixes

* **lowercase-name:** consider skip and only prefixes for ignores ([#923](#923)) ([8716c24](8716c24))
* **prefer-to-be:** don't consider RegExp literals as `toBe`-able ([#922](#922)) ([99b6d42](99b6d42))

### Features

* create `require-hook` rule ([#929](#929)) ([6204b31](6204b31))
* deprecate `prefer-to-be-null` rule ([4db9161](4db9161))
* deprecate `prefer-to-be-undefined` rule ([fa08f09](fa08f09))
* **valid-expect-in-promise:** re-implement rule ([#916](#916)) ([7a49c58](7a49c58))
@github-actions
Copy link

🎉 This PR is included in version 25.0.0-next.6 🎉

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.

prefer-to-be considers RegExp literal notation as a literal

2 participants