Skip to content

Support custom exporters via --exporters option - #3212

Merged
timcassell merged 1 commit into
dotnet:masterfrom
sheddy123:feature/1967-custom-exporters
Jul 29, 2026
Merged

timcassell merged 1 commit into
dotnet:masterfrom
sheddy123:feature/1967-custom-exporters

Conversation

@sheddy123

Copy link
Copy Markdown
Contributor

#1967

Support custom exporters via --exporters option

Allow specifying custom IExporter types by assembly-qualified name in the --exporters CLI option. Added TryResolveExporters for unified resolution and validation of exporters. Extended tests to cover custom exporters, combinations with built-ins, and error handling for invalid types.

Support custom exporters via --exporters option

Allow specifying custom IExporter types by assembly-qualified name in the --exporters CLI option.
Added TryResolveExporters for unified resolution and validation of exporters. Extended tests to cover custom exporters, combinations with built-ins, and error handling for invalid types.

@timcassell timcassell left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. It's same as idea as previous PR, but other maintainers didn't leave any comments, so LGTM. Providing a RegisterCustomExporter API seems a bit overkill anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom exporter options to be defined

2 participants