Feat: parameterize pipeline class in the primary factory method

[z3z1ma]

Description

This is an easy addition to parameterize and will simplify some hackery in cdf. Furthermore it makes the factory method significantly more flexible in possibilities since we can pass subclasses of Pipeline.

Related Issues

• Fixes #...
• Closes #...
• Resolves #...

Additional Context

In the future, it would be even simpler if this sort of factory method was a classmethod on the Pipeline class and simply aliased/exported like pipeline = Pipeline.create where Pipeline.create has a sig like def create(cls, ...) which also lets subclasses benefit from the "standard" setup procedure.

For now, we make the simpler change though...

[netlify]

✅ Deploy Preview for dlt-hub-docs ready!

Name	Link
🔨 Latest commit	48cdfa1
🔍 Latest deploy log	https://app.netlify.com/sites/dlt-hub-docs/deploys/6612e0f84536560008535dba
😎 Deploy Preview	https://deploy-preview-1176--dlt-hub-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rudolfix]

for some reason linter is not able to assign types to instances of pipeline created via dlt.pipeline. looks weird. maybe try to temporarily remove the pipeline()` overload (it is not parametrized)

somehow this worked with DltSource

[rudolfix]

@z3z1ma OK I know what the problem is. there's a special TypeVar in typing extensions that let's you to set a default. I spend several hours looking for this when upgrading DltSoure. See 48cdfa1

is this PR doing what you need in CDF now?

[z3z1ma]

Ah I definitely would not have found that for some time 😅

Thanks for the update @rudolfix 🙌

I just tried it out and indeed it works perfectly. This is very powerful.