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.