Currently Job.config is a bespoke implementation used only for the throttling logic, which is a leak in the Job abstraction. In order to move the throttling logic into it's own layer Jobs needd a general purpose metadata hash which is accessible in a before_run hook (#69).
Currently Job.config is a bespoke implementation used only for the throttling logic, which is a leak in the Job abstraction. In order to move the throttling logic into it's own layer Jobs needd a general purpose metadata hash which is accessible in a before_run hook (#69).