fix(no-await-sync-events): stop reporting user-event by default

[Belco90]

Checks

• I have read the contributing guidelines.

Changes

• Stop reporting user-event methods by default, assuming v14 is the standard now.

Context

Fixes #801
Fixes #669

[MichaelDeBoey]

We should release this in a major release btw as this is breaking behavior for this specific rule and people need to adjust their config if they want the current released functionality (for instance when only enabling this specific rule)

[Belco90]

We should release this in a major release btw as this is breaking behavior for this specific rule and people need to adjust their config if they want the current released functionality (for instance when only enabling this specific rule)

Not really. In our semantic version policy, we specify that a bug fix in a rule that results in eslint-plugin-testing-library reporting fewer errors will be a patch release.

The rule was reporting both fire-event and user-event. The change done here is to report only fire-event by default. The changes in the presets were needed to reflect the new default change correctly. However, the actual config of the rule and the way it reports the errors are the same.

I get the point of your comment, tho. A change in the number of errors reported could potentially be a breaking change. That's why we defined the semver policy, inspired by ESLint semver policity itself, so users know what to expect.

[github-actions]

🎉 This PR is included in version 6.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀