-
Notifications
You must be signed in to change notification settings - Fork 5
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
install watch reaction function to fake client #550
base: main
Are you sure you want to change the base?
install watch reaction function to fake client #550
Conversation
Signed-off-by: Ashish Naware <[email protected]>
c189e97
to
c533767
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #550 +/- ##
==========================================
- Coverage 58.93% 58.85% -0.09%
==========================================
Files 33 33
Lines 2981 2987 +6
==========================================
+ Hits 1757 1758 +1
- Misses 1130 1134 +4
- Partials 94 95 +1 ☔ View full report in Codecov by Sentry. |
Hi @AshishNaware. Thanks for the contribution. This change is heading in the right direction, but is also incomplete as it has no runtime effect. Let me know if you need any pointers into the code base. |
Hey. Thanks for the feedback. Let me dig more into the code-base. I will create a thread here if i have any questions :) |
@scothis - I just took a quick glance at the code and I see a Watch method already implemented for duckAwareClientWrapper that returns a watch.Interface. I assume that we need a similar implementation for the clientWrapper as well. thoughts? |
Yep. This is also where the watch reaction funcs should be applied. |
This PR adds ability to install watch reaction function to the fake client. This will help in writing tests where its required to simulate behavior of the watcher.