-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
feat(Visibility): add updateOn
prop
#2791
Conversation
c3a9a12
to
cc3f0e6
Compare
cc3f0e6
to
d59010e
Compare
Codecov Report
@@ Coverage Diff @@
## master #2791 +/- ##
==========================================
+ Coverage 99.74% 99.74% +<.01%
==========================================
Files 160 160
Lines 2773 2777 +4
==========================================
+ Hits 2766 2770 +4
Misses 7 7
Continue to review full report at Codecov.
|
@@ -537,4 +537,36 @@ describe('Visibility', () => { | |||
}) | |||
}) | |||
}) | |||
|
|||
describe('updateOn', () => { |
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.
We should add a test here that it()
defaults to events
. Also, it would be great to have an event based assertion to ensure that events are still working.
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.
I added a new test to test the default value. All other tests work with events, so I don't think that we need to duplicate any of them.
❤️ |
…React into feat/visibility-update-on
7fc8616
to
a364d0c
Compare
a364d0c
to
2e069c3
Compare
Refs #2318.