-
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
motion methods should use ShortName() #1560
motion methods should use ShortName() #1560
Conversation
shouldn't we update other parts to accept a full name? short name is riskier |
@edaniels Isn't that functionally what this is doing? Counterintuitively, The only information that's not captured in ShortName is the subtype, but we shouldn't care about that for framesystem stuff, since ShortName should always be unique in a robot. |
there's the .String() which is the fully qualified name with all remotes involved |
.String() is subtype/remote:component, whereas ShortName is just remote:component. Remote:component is what the framesystem uses, so that's what should be used here. If we want the framesystem to use subtype/remote:component I'm not opposed to that but that should be coordinated with the RDK Components team, and also we probably shouldn't block this PR on that; this will fix the system as it currently exists, and that would be an improvement that re-updating this would be a part of. |
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
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.
Yay short name
ah, yes. my bad! |
…y-stripping-off-remote-name
|
No description provided.