-
Notifications
You must be signed in to change notification settings - Fork 147
v6.0.0 #796
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
Conversation
BREAKING CHANGE: `prefer-wait-for` is now removed
BREAKING CHANGE: `no-render-in-setup` is now called `no-render-in-lifecycle`
BREAKING CHANGE: `no-manual-cleanup` is now enabled by default in the React & Vue configs
…660) BREAKING CHANGE: `no-global-regexp-flag-in-query` is now enabled by default in all configs
…or `user-event` (#652) BREAKING CHANGE: `await-fire-event` is now called `await-async-event`
BREAKING CHANGE: `no-node-access` is now enabled by default in the DOM config
…default (#663) BREAKING CHANGE: `no-debugging-utils` now enables all debug methods in all configs by default
BREAKING CHANGE: `no-await-sync-query` is now called `no-await-sync-queries`
…fault (#667) BREAKING CHANGE: `no-await-sync-events` is now enabled by default in the DOM, Angular & React configs
BREAKING CHANGE: `await-async-query` is now called `await-async-queries`
# Conflicts: # README.md # docs/rules/await-fire-event.md # docs/rules/no-render-in-lifecycle.md # docs/rules/prefer-wait-for.md # lib/rules/await-fire-event.ts # tests/__snapshots__/index.test.ts.snap # tests/index.test.ts # tests/lib/rules/await-fire-event.test.ts
# Conflicts: # README.md # lib/rules/no-debugging-utils.ts # tests/index.test.ts
I need to install the |
Tested by installing the alpha in other projects. All good! |
dom: ['error', { eventModule: 'userEvent' }], | ||
angular: ['error', { eventModule: 'userEvent' }], | ||
react: ['error', { eventModule: 'userEvent' }], |
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.
Should we use an array here as well for consistency?
dom: ['error', { eventModule: 'userEvent' }], | |
angular: ['error', { eventModule: 'userEvent' }], | |
react: ['error', { eventModule: 'userEvent' }], | |
dom: ['error', { eventModule: ['userEvent'] }], | |
angular: ['error', { eventModule: ['userEvent'] }], | |
react: ['error', { eventModule: ['userEvent'] }], |
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.
Both ways are accepted, and we are only setting one value, so it's fine.
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Checks
Changes
This PR contains all the changes for v6.0.0. You can install it via the
alpha
tag before it gets released officially.Context
n/a