Closed leandropineda closed 3 years ago
I was able to capture the unexpected rosFrameToPlanarDatumUUID
property on the Identity report message by implementing schema checking before sending each message.
[ERROR] [1624993135.448303037] [MassRoboticsAMRInteropNode]: Invalid schema for '<class 'massrobotics_amr_sender.messages.IdentityReport'>' message. The error reported is: 'Additional properties are not allowed ('rosFrameToPlanarDatumUUID' was unexpected)'. Ignoring message.
This also captured other minor issues on Status report messages
[ERROR] [1624993136.693667449] [MassRoboticsAMRInteropNode]: Invalid schema for '<class 'massrobotics_amr_sender.messages.StatusReport'>' message. The error reported is: ''foo' is not one of ['navigating', 'idle', 'disabled', 'offline', 'charging', 'waiting', 'loadingUnloading', 'manualOveride']'. Ignoring message.
LGTM @leandropineda great work and great PR description!
Changes
additionalProperties
keyword to schemas to be able to detect unexpected properties.rosFrameToPlanarDatumUUID
on Identity Report.Demo
Identity Report
Status report with invalid data