Invoking the generalized "call-block-logs" transformation strategy twice in a row to filter for different events would cause them all to be written into the same file #258
And if we'd run both of these one after each other, all their results would go to "datadir/call-block-logs-transformation"
What has changed is that the strategies are now general purpose retrieval functions that can be controlled with their arguments, whereas blueprints are more opinionated and feature actual platform business logic
So a blueprint should be allowed to e.g. control the file name a transformer can write to, e.g. in the crawl path