refactor: EtlPipeline entry via Create() instance seed (Option 2) - #280
Merged
Conversation
…n 2)
Replaces the static EtlPipeline class + EtlPipelineSource sentinel with a
sealed instance class: EtlPipeline.Create() returns a fresh seed, and the
From factories become instance methods. Format packages now extend the
EtlPipeline instance directly (this EtlPipeline) instead of a separate
sentinel type, e.g. EtlPipeline.Create().CsvExtractor<Order>("orders.csv").
Removes EtlPipelineSource, updates PublicAPI, Example8 (net4.8 + net8.0),
the EtlPipeline unit tests, and the CHANGELOG 0.16.0 entry. Pipeline core
(IEtlPipeline<T> Through/To, IEtlPipelineSink, impl) is unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Chris-Wolfgang
commented
Jul 20, 2026
This was referenced Jul 20, 2026
This was referenced Jul 22, 2026
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switches the
EtlPipelineentry point from the static-class +Sourcesentinel design to the instance seed design we settled on (Option 2), so it can ship with 0.16.0.Changes
EtlPipeline:public static class→public sealed classwith a private ctor and staticCreate(); theFromfactories become instance methods.EtlPipelineSource— theEtlPipelineinstance is now the extension receiver for format-package source factories (this EtlPipeline), so the separate sentinel is obsolete.PublicAPI.Shipped.txt,Example8-EtlPipeline(net4.8 + net8.0), theEtlPipelineunit tests, and the CHANGELOG 0.16.0 entry.Unchanged
The pipeline core is untouched —
IEtlPipeline<T>(Through/To/AsAsyncEnumerable),IEtlPipelineSink,EtlPipelineImpl,EtlPipelineProgress, run-state. Only the entry point changed.Why
Create()returning a fresh instance reads honestly as "start a pipeline," removes the.Sourcenaming/asymmetry wart, keeps the unifiedEtlPipelineprefix, and gives pipeline-level config a natural home on the seed if ever needed. One type instead of two.Test plan
dotnet build -c Releaseclean across all 11 TFMsFrom/Through/To/cancellation/progress + newCreate_returns_a_new_instance_each_callCreate()Note on operators
Per the core's own design (and this PR's docs), the LINQ operators (
Where/Select/Distinct) live inWolfgang.Etl.Transformersas extensions onThrough, not here — out of scope for this entry-point change.🤖 Generated with Claude Code