Currently, when a ReportNode has children, the parent node is often created way before the children, leading to a message which has little value, except that it groups nodes. There's currently no way to sum up the sub-reportNodes, as there's no way to add values to the parent node after its creation.
Describe the expected behavior
Enrich the API to be able to easily sum up the content of the sub-reportNodes.
Describe the motivation
Some users use ReportNode functional logging as a way to see the tree of the processes launched, due to the previous Reporter API, which separated reporter (nodes) and report (leaves). The new ReportNode API does not provide this distinction anymore, but there's currently no easy way to provide much more information, as the displayed values are needed at the parent creation.
Describe the current behavior
Currently, when a ReportNode has children, the parent node is often created way before the children, leading to a message which has little value, except that it groups nodes. There's currently no way to sum up the sub-reportNodes, as there's no way to add values to the parent node after its creation.
Describe the expected behavior
Enrich the API to be able to easily sum up the content of the sub-reportNodes.
Describe the motivation
Some users use ReportNode functional logging as a way to see the tree of the processes launched, due to the previous Reporter API, which separated reporter (nodes) and report (leaves). The new ReportNode API does not provide this distinction anymore, but there's currently no easy way to provide much more information, as the displayed values are needed at the parent creation.
Extra Information
No response