You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
no-await-sync-events must not report user-event methods by default since it aims user-event v14, so only fire-event it's reported. However, we need an option to decide which methods to be reported: fire-event, user-event or both.
The idea is to include an option in the same way as #626 with the following values for presets:
dom: rule enabled with fire-event
angular: rule enabled with fire-event
react: rule enabled with fire-event
vue: rule not enabled
marko: rule not enabled
The text was updated successfully, but these errors were encountered:
Does there need to be a user-event option at all, or is the idea to still support user-event versions before v14 on v6 of this package which means it would still be needed?
The idea is to still support user-event versions before v14 on v6 of the plugin. We did the same for await-async-events so by default it reports user-event as async, but can be disabled to provide backward compatibility for user-event prior to v14. Same here, so by default it doesn't report user-event as sync, unless it's enabled through its options.
no-await-sync-events
must not report user-event methods by default since it aims user-event v14, so only fire-event it's reported. However, we need an option to decide which methods to be reported: fire-event, user-event or both.The idea is to include an option in the same way as #626 with the following values for presets:
The text was updated successfully, but these errors were encountered: