dotnet/BenchmarkDotNet

Allow custom exporter options to be defined

Open

Aperta il 26 mar 2022

Vedi su GitHub
 (8 commenti) (0 reazioni) (0 assegnatari)C# (11.415 star) (1054 fork)batch import
Area:CommandLineArea:Exportersenhancementgood first issueup-for-grabs

Descrizione

Currently options for the exporters console argument are hardcoded here: https://github.com/dotnet/BenchmarkDotNet/blob/21a29406406aeca1cdfa195fa86ac28d04ba8e33/src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs#L52-L71

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

Guida contributor

Tech stack
csharp
Dominio
tooling
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
C# knowledgefamiliarity with BenchmarkDotNet exporter system
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60
Direzione di ricerca
The issue requests the ability to add custom exporter options to the console argument list. Currently, options are hardcoded in ConfigParser.cs (lines 52-71). A solution would involve refactoring that section to accept a dynamic list of exporter options, possibly via a registration mechanism. Review the existing exporter classes and the way they are currently processed. Consider adding an interface or abstract class that custom exporters can implement to provide their own options. Then modify the ConfigParser to iterate over all registered exporters and collect their options.