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
Is your feature request related to a problem? Please describe.
Some users either aren't aware about user-event because it's not mentioned by the documentation, or want to use it but find the documentation harder to find.
Describe the solution you'd like
Move at least the API documentation in user-event's readme to a prominent page in the sidebar of the docs. This should be in a format similar to fireEvent to make it easier to learn, but still in a separate section so users are aware they have to install another package. Overall, it should be clear that this is recommended, but still not actually a part of the other testing libraries.
Additional context
This could also make it easier to migrate user-event back into dom-testing-library in the future.
There's already a user-event page in the docs, but there are still some differences between the docs page and the readme. In order to remove this content from user-event, we'll need to make sure they're in sync first.
Is your feature request related to a problem? Please describe.
Some users either aren't aware about user-event because it's not mentioned by the documentation, or want to use it but find the documentation harder to find.
Describe the solution you'd like
Move at least the API documentation in user-event's readme to a prominent page in the sidebar of the docs. This should be in a format similar to fireEvent to make it easier to learn, but still in a separate section so users are aware they have to install another package. Overall, it should be clear that this is recommended, but still not actually a part of the other testing libraries.
Additional context
This could also make it easier to migrate user-event back into dom-testing-library in the future.
Related issues
user-event
,jest-dom
are putting in small *ecosystem*? Those are de facto stuff within@testing-library/react
as almost React devs. #515The text was updated successfully, but these errors were encountered: