-
Notifications
You must be signed in to change notification settings - Fork 1
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: bunch of updates #5
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Awesome! Thanks for your dedication to this project. 🎉 |
SimenB
approved these changes
Jul 5, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏
github-actions bot
pushed a commit
that referenced
this pull request
Aug 15, 2022
# 1.0.0 (2022-08-15) ### Features * bunch of updates ([#5](#5)) ([8e45c68](8e45c68)) * create `prefer-to-be-array` rule ([9bd067c](9bd067c)) * create `prefer-to-be-false` rule ([b35e45c](b35e45c)) * create `prefer-to-be-object` rule ([676de1d](676de1d)) * create `prefer-to-be-true` rule ([22f8093](22f8093)) * initial commit ([3ed88c4](3ed88c4))
🎉 This PR is included in version 1.0.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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the plugin to be aligned with the structure & versions of
eslint-plugin-jest
, meaning we're now requiring Node v12 or higher, support ESLint v6 and higher (dropping support for v5), and using the latest major of@typescript-eslint
.Technically this is very breaking, but we don't have a v1 released yet so it should be fine 😄
I've not applied extra changes like the updating the utils, setting up the
regenerate-docs
tool, setting up a weekly smoke test, or refactoring the rules & utils with general tricks and improvements I've learnt over the last 2+ years while working oneslint-plugin-jest
- I'll do that sort of stuff later.Relates to #2