Allow custom exporter options to be defined

[PaulRitter]

Currently options for the exporters console argument are hardcoded here:

BenchmarkDotNet/src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs

Lines 52 to 71 in 21a2940

	private static readonly IReadOnlyDictionary<string, IExporter[]> AvailableExporters =
	new Dictionary<string, IExporter[]>(StringComparer.InvariantCultureIgnoreCase)
	{
	{ "csv", new[] { CsvExporter.Default } },
	{ "csvmeasurements", new[] { CsvMeasurementsExporter.Default } },
	{ "html", new[] { HtmlExporter.Default } },
	{ "markdown", new[] { MarkdownExporter.Default } },
	{ "atlassian", new[] { MarkdownExporter.Atlassian } },
	{ "stackoverflow", new[] { MarkdownExporter.StackOverflow } },
	{ "github", new[] { MarkdownExporter.GitHub } },
	{ "plain", new[] { PlainExporter.Default } },
	{ "rplot", new[] { CsvMeasurementsExporter.Default, RPlotExporter.Default } }, // R Plots depends on having the full measurements available
	{ "json", new[] { JsonExporter.Default } },
	{ "briefjson", new[] { JsonExporter.Brief } },
	{ "fulljson", new[] { JsonExporter.Full } },
	{ "asciidoc", new[] { AsciiDocExporter.Default } },
	{ "xml", new[] { XmlExporter.Default } },
	{ "briefxml", new[] { XmlExporter.Brief } },
	{ "fullxml", new[] { XmlExporter.Full } }
	};

I would love a way to add custom exporters as options to this list.

[PaulRitter]

nevermind. it appears you can define custom exporters using the IConfig

[PaulRitter]

actually, i will reopen this since it would be nice to be able to define exporter-options which are selectable over the args.

[adamsitnik]

i will reopen this since it would be nice to be able to define exporter-options which are selectable over the args.

@PaulRitter Could you please elaborate more on that? Please provide sample API design and code example.

[PaulRitter]

i will reopen this since it would be nice to be able to define exporter-options which are selectable over the args.

@PaulRitter Could you please elaborate more on that? Please provide sample API design and code example.

I updated the original comment, did that clear it up? Otherwise im open to thinking a bit more on the idea and coming up with an entire API proposal, but i'd have to get more familiar with the project for that.

[adamsitnik]

@PaulRitter now I get it: you would like to have the possibility to extend the existing command line argument parsing logic with the possibility to specify user-defined exporters so you can do sth like --exporter myExporter.

We could introduce a new method:

public static class ConfigParser
{
   public static void RegisterCustomExporter(string commandLineName, IExporter exporter) => AvailableExporters.Add(commandLineName, exporter);
}

@PaulRitter if that is what you need please send a PR.