You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When querying for devices, a map of device name to all of the protocols it matches are shown.
When querying for a specific device, root or child device names can be used, to give the protocols of a child device.
However, there is no way of knowing what children a device has.
e.g. SimStage, which has children of x & y: both are Movables, but without knowing that SimStage has these children, you cannot find them.
Acceptance Criteria
There is a way of finding out about the children of a root device
This could be that querying for devices gives you the full tree of its children, grandchildren etc.
This could be that querying for a device takes an optional "children: bool" or "depth: int" parameter to decide how completely to interrogate the device's tree.
This could be a new query, with the above optional arguments
When querying for devices, a map of device name to all of the protocols it matches are shown.
When querying for a specific device, root or child device names can be used, to give the protocols of a child device.
However, there is no way of knowing what children a device has.
e.g. SimStage, which has children of x & y: both are Movables, but without knowing that SimStage has these children, you cannot find them.
Acceptance Criteria
parent-childis registered to the blueapi context and can be fetched and displayed, which would fix Enumerate nested devices in plan schemas #1129 also for free?