-
Notifications
You must be signed in to change notification settings - Fork 111
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
Make missing rpc client registration fail with more verbose message #1661
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When circumventing the FromRobot(r) helpers, like one may do if they are new to the RDK, the likely result of trying to address any one of r.ResourceNames is going to lead to the ErrMissingClientRegistration. If said soul is familiar with Go own flavor of DI package registration it's easy to find the x/register packages (and probably the helpers in the process). However a slight nudge never hurt anyone.
stuqdog
reviewed
Dec 14, 2022
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.
Hi @ermik! Thanks so much for making this change. One minor nitpick but in general this looks good :)
stuqdog
added
the
safe to test
This pull request is marked safe to test from a trusted zone
label
Dec 14, 2022
Co-authored-by: Ethan <ethan@viam.com>
viambot
removed
the
safe to test
This pull request is marked safe to test from a trusted zone
label
Dec 16, 2022
edaniels
added
the
safe to test
This pull request is marked safe to test from a trusted zone
label
Dec 16, 2022
|
edaniels
changed the title
Developer experience: make missing clients fail more verbose
Make missing rpc client registration fail with more verbose message
Dec 16, 2022
stuqdog
approved these changes
Dec 16, 2022
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!
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When circumventing the
FromRobot(r)
helpers, like one may do if they are new to the RDK, the likely result of trying to address any one ofr.ResourceNames
is going to lead to theErrMissingClientRegistration
. If said soul is familiar with Go own flavor of DI package registration it's easy to find the x/register packages (and probably the helpers in the process). However a slight nudge never hurt anyone?