Uh oh!
There was an error while loading. Please reload this page.
Add validation to Robot CRD for properties of status quo - #41
Add validation to Robot CRD for properties of status quo#41oliver-goetz wants to merge 4 commits into
Conversation
| lastStateChangeTime: | ||
| type: string | ||
| batteryPercentage: | ||
| type: number |
There was a problem hiding this comment.
I would prefer to not have batteryPercentage here. If one wants to do planning based on robot conditions, we'll probably need lots of predicates and this might be too much overload for the status api.
There was a problem hiding this comment.
That's fine with me. We probably should remove it from Go and protobuf data type too. What do you think?
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ensonic
commented
Apr 27, 2020
Alright, could you please reword the title. Instead of ' improve the reusability' maybe say that we add validation to the schema. For the batteryPercentage and trolleAtached we'll keep this in, but please file a new bug, we should think of a more flexible way to transport such data without beeing application specific. |
oliver-goetz
commented
Apr 28, 2020
okay done |
Added
Statusattribute to GoRobotCRD data type to improve the reusability of the packageThese are the changes of this pull request:
RobotStatusRobotdata type to latest versionrobots.registry.cloudrobotics.comto ensure that Robot CRD watcher of approllout controller always receives valid CRs