Use CsvHelper in export action

[bjarnef]

While looking at the Umbraco UI Builder demo, it noticed ExportEntityAction and ImportEntityAction.

ImportEntityAction use CsvHelper:

is there any reason ExportEntityAction doesn't use it as well?

It could eventually has a configuration to select delimiter or how quotes should be handled?

[mattbrailsford]

I think it was likely that that export came first, and exporting requires less forgiving code and so when dealing with imports, the CsvHelper was used. Is there an issue with export that would suggest CsvHelper should be used?

[bjarnef]

I guess it could be an issue if the field contains comma or e.g. using tags as comma delimited strings.
We have also used CsvHelper in some projects with locations, where some of the chars in names caused some issues, where it was used in import (not Konstrukt/Umbraco UI Builder though)

var config = new CsvConfiguration(CultureInfo.InvariantCulture)
{
    Delimiter = ",",
    DetectColumnCountChanges = true,
    HasHeaderRecord = true,
    HeaderValidated = null,
    MissingFieldFound = null,
    IgnoreBlankLines = false,
    Mode = CsvMode.RFC4180,
    // Ignore header case.
    PrepareHeaderForMatch = args => args.Header.ToLower()
};

[mattbrailsford]

Commas should be covered by the EscapeCsvValue call, but good point on the special chars. I'll have a look at updating it to use CsvHelper 👍

[bjarnef]

Regarding the Import action it didn't seem to do anything in UI Builder demo? Is it due of missing configuration?

Reported it here: umbraco/Umbraco.UIBuilder.Demo#4 but feel maybe it is in UI Builder itself the issue exist.