Describe the new feature you would like to see
Return an error when trying to queue a mission containing tasks not supported by the given robot. For instance if trying to take a thermal video with a robot that does not have a thermal camera. For simplicity we can focus on the backend part of this task in this issue, but as long as we return a 400 status code then this will anyways be reported in the frontend.
Describe the solution you'd like
We can check the tasks in the mission and compare them to the RobotCapabilites field in Robot.cs. If the list is null then we should assume that it is allowed.
How will this feature affect the current Threat Model?
N/A
Describe the new feature you would like to see Return an error when trying to queue a mission containing tasks not supported by the given robot. For instance if trying to take a thermal video with a robot that does not have a thermal camera. For simplicity we can focus on the backend part of this task in this issue, but as long as we return a 400 status code then this will anyways be reported in the frontend.
Describe the solution you'd like We can check the tasks in the mission and compare them to the RobotCapabilites field in Robot.cs. If the list is null then we should assume that it is allowed.
How will this feature affect the current Threat Model? N/A