One does not simply @Inject in TPF
I remember IntelliJ IDEA constantly nudging me away from field injection and toward constructor parameters. Funny how relevant that feels now. The principle was sound: make dependencies explicit. A pipeline should say what it needs, where it comes from, and how it flows—without invisible framework magic: TPF applies that instinct to the whole application. https://pipelineframework.org
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.