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
Hello! I'm working on an upgrade to v14. The async API has helped smooth out a lot of our test code. So thanks!
During review I got asked a question about the long term stability of the direct API calls. The question mostly comes from this statement in the documentation.
Note that, while directly invoking APIs such as userEvent.click() (which will trigger setup internally) is still supported in v14, this option exists to ease the migration from v13 to v14, and for simple tests. We recommend using the methods on the instances returned by userEvent.setup().
Are we to understand that directly invoking the APIs will eventually be deprecated or removed? Or is the intent to provide continued support for that style? Perhaps someone could explain the preference to use setup() when the direct API does it already. That might help me understand.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello! I'm working on an upgrade to v14. The async API has helped smooth out a lot of our test code. So thanks!
During review I got asked a question about the long term stability of the direct API calls. The question mostly comes from this statement in the documentation.
Are we to understand that directly invoking the APIs will eventually be deprecated or removed? Or is the intent to provide continued support for that style? Perhaps someone could explain the preference to use
setup()
when the direct API does it already. That might help me understand.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions