prefer-user-event should consider the use case where fireEvent is used as a function

[gndelia]

In addition to the method events like fireEvent.click, it is also possible to create custom events objects and use fireEvent as a function, as the documentation for fireEvent shows

// form 1
const myEvent = createEvent.click(node)
fireEvent(node, myEvent)

// form 2
fireEvent(
  input,
  createEvent('click', input)
)

The rule should recommend to use userEvent.click()

the rule should consider this form too

Note: This rule has been migrated in the v4 branch, so anyone taking this issue should do so starting from branch v4 (And targeting it as well)

[Belco90]

This one must wait until v4 is released.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gndelia]

now that v4 is released, we can tackle this one. I think I can tackle it the next week, so if no one takes it during that time, I might do so

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gndelia]

I'm taking this one so stale bot doesn't close it 😆 I'll tackle it during the week

[github-actions]

🎉 This issue has been resolved in version 4.7.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀