Our wiki does not contain enough or seemingly any info on string or number literals within a "normal" chart.
It seems we may have implemented the base-functionality but not tested and documented it thoroughly.
Note: This way of setting literals appears to have been added in: #1926
"The issue to directly edit existing arrays remain..." This is essentially that bug as it was never resolved.
It is possible to set e.g. chart.Series[0].XSeries = $"{{'Test{1}','Test{2}'}}";
To set 2 string literals in the xSeries of a chart or e.g.
chart.Series[0].Series= $"{{{1},2}}}"; To set number literals.
This should be documented somewhere. And Ideally literals should have 1-2 samples in the sample project.
In addition the implementation of literals should be tested more thoroughly. Reading in a chart and then applying:
chart.Series[0].XSeries = $"{{'Test{1}','Test{2}'}}"; when the chart already has range values. Will silently cause a corrupt workbook on save as it will have both literals and non-literals on the same chart
Our wiki does not contain enough or seemingly any info on string or number literals within a "normal" chart.
It seems we may have implemented the base-functionality but not tested and documented it thoroughly.
Note: This way of setting literals appears to have been added in: #1926
"The issue to directly edit existing arrays remain..." This is essentially that bug as it was never resolved.
It is possible to set e.g.
chart.Series[0].XSeries = $"{{'Test{1}','Test{2}'}}";To set 2 string literals in the xSeries of a chart or e.g.
chart.Series[0].Series= $"{{{1},2}}}";To set number literals.This should be documented somewhere. And Ideally literals should have 1-2 samples in the sample project.
In addition the implementation of literals should be tested more thoroughly. Reading in a chart and then applying:
chart.Series[0].XSeries = $"{{'Test{1}','Test{2}'}}";when the chart already has range values. Will silently cause a corrupt workbook on save as it will have both literals and non-literals on the same chart