dotnet/BenchmarkDotNet

Allow custom exporter options to be defined

Open

#1,967 建立於 2022年3月26日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)C# (11,415 star) (1,054 fork)batch import
Area:CommandLineArea:Exportersenhancementgood first issueup-for-grabs

描述

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.

貢獻者指南

技術棧
csharp
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C# knowledgefamiliarity with BenchmarkDotNet exporter system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.