It would be nice to be able to define a job which can exist on multiple tubes (by using tube_names "foo", "bar", "baz" at class scope) and have some way of specifying which tube it should be enqueued into. Right now, the best option (since we can't subclass jobs) is to have two identical jobs whose logic lives in a common mixin, which is not fantastic.
It would be nice to be able to define a job which can exist on multiple tubes (by using
tube_names "foo", "bar", "baz"at class scope) and have some way of specifying which tube it should be enqueued into. Right now, the best option (since we can't subclass jobs) is to have two identical jobs whose logic lives in a common mixin, which is not fantastic.