Not sure if correct place, but is there a technical reason why the imperative api doesn’t exist in prefect 2.0? I found it very helpful when building tasks with reusable logic and tasks that have other class methods benefiting from the encapsulation the imperative api provides. (More in thread)

check this https://discourse.prefect.io/t/can-i-define-my-tasks-as-classes-rather-than-functions/54

I will take a look at that I am currently working on migrating over to 2.0, but all of our workflows’ tasks are subclasses of

Task

I suppose some class methods could be tasks in themselves, but when thinking about design of individual units of work I like to keep logic packed into 1 task without having a ton of logic in the

run

method