Open oliver-sanders opened 1 year ago
(I think it will be easier to maintain this list server-side than trying to maintain it client-side, hence a cylc-flow issue)
Just realised, when we have offline data in the GUI this field may not reflect the truth so this issue might require a little more thought.
Add a flow_nums field to the
workflow
thinggy in GraphQL.We already have
TaskProxy.flow_nums
which gives the flow numbers for a given task. To assist with https://github.com/cylc/cylc-ui/issues/470 we could do with a flow_nums field which contains all combinations of flow numbers in the store.E.G: If we have the following tasks in the store:
Then we would expect
Workflows.flow_nums
to contain all unique flow number combinations i.e:The UI can then use this information to provide consistent visual filtering with the aim of making flows visible across all views in the GUI.
This work becomes important with #5643 which will strip flow numbers from tasks.