-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistently track modal events #1007
Conversation
🦋 Changeset detectedLatest commit: 6c10a02 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sumup/oss-circuit-ui/GtdTTDR4FBKi184mpNfc5TxsH2mv |
Codecov Report
@@ Coverage Diff @@
## next #1007 +/- ##
==========================================
- Coverage 90.99% 90.96% -0.04%
==========================================
Files 160 161 +1
Lines 2665 2666 +1
Branches 765 763 -2
==========================================
Hits 2425 2425
- Misses 215 217 +2
+ Partials 25 24 -1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Purpose
While migrating the dashboard to the new Modal API (#949), I realized that modal events aren't tracked consistently depending on how a modal is opened or closed. The logic is duplicated in several places which allowed for inconsistencies.
Approach and changes
useModal
hook into theModalProvider
component. Added tests to verify that tracking events are dispatched no matter how the model is triggered.Definition of done