add several limits with line catalog

[EtienneLt]

PR Summary

• linked with allow to have a list of temporary limits in line catalog network-modification-server#764
• allow to manage several temporary limits with line catalog

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Mathieu-Deharbe]

temporaryLimitsNamesForCatalog may be undefined. It definitely will be in the default config.

[EtienneLt]

'?' is missing no ?

[Mathieu-Deharbe]

I didn't test but you should have to do that part out of the metadata loop :

base.push({
                        headerName: `${limitName} [A]`,
                        field: limitName,
                        cellRenderer: DefaultCellRenderer,
                    });

[Mathieu-Deharbe]

Because of this the data can't be seen from this interface if temporaryLimitsNamesForCatalog is undefined :

Which could be a fine design (if the POs agree) but then when I validate I have data :

I think we should ignore the data that are not defined in temporaryLimitsNamesForCatalog OR still load the data and display it.

[Mathieu-Deharbe]

I didn't test but you should have to do that part out of the metadata loop :

base.push({
                        headerName: `${limitName} [A]`,
                        field: limitName,
                        cellRenderer: DefaultCellRenderer,
                    });

[Mathieu-Deharbe]

Suggested change

	export type TemporaryLimitSelectedRowData = Record<string, number | string>
	export type TemporaryLimitSelectedRowData = Record<string, number | string>;

[Mathieu-Deharbe]

Because of this the data can't be seen from this interface if temporaryLimitsNamesForCatalog is undefined :

Which could be a fine design (if the POs agree) but then when I validate I have data :

I think we should ignore the data that are not defined in temporaryLimitsNamesForCatalog OR still load the data and display it.