-
Notifications
You must be signed in to change notification settings - Fork 84
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(sdk): Use v2 Command Client #845
Conversation
Codecov Report
@@ Coverage Diff @@
## master #845 +/- ##
==========================================
- Coverage 62.79% 62.77% -0.02%
==========================================
Files 31 31
Lines 1981 1980 -1
==========================================
- Hits 1244 1243 -1
Misses 647 647
Partials 90 90
Continue to review full report at Codecov.
|
@@ -63,10 +63,10 @@ func NotificationsClientFrom(get di.Get) notifications.NotificationsClient { | |||
var CommandClientName = di.TypeInstanceToName((*command.CommandClient)(nil)) |
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.
change command.CommandClient
to interfaces.CommandClient
Register v2 client in dic and change interface used throughout. Signed-off-by: Alex Ullrich <[email protected]>
22ed9b3
to
89e9755
Compare
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.
LGTM
Register v2 client in dic and change interface used throughout.
Signed-off-by: Alex Ullrich [email protected]
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
v1 client is still exposed to custom services by the SDK, does not work with commands routed to v2 device services.
Issue Number: #844
What is the new behavior?
v2 client is registered with dic and interface used in references throughout.
Does this PR introduce a breaking change?
Yes this will break any usages of the client retrieved through context.CommandClient() by returning a new interface.
Are there any new imports or modules? If so, what are they used for and why?
Are there any specific instructions or things that should be known prior to reviewing?
I updated the mocks by hand since I didn't want to worry about mockery version or usage differences messing something up.
Other information