Deprecate the processors module option about bull HOT 5 CLOSED

Oopsie, I totally forgot about that feature. I'll come back to you with a proper implementation / example.

from bull.

Ok. I've had some time to think about this and I've come to the conclusion that the processors option should not be deprecated.

However, this options' type will change from

export type BullQueueProcessor =
  BullQueueProcessorCallback // (job: Job, done: DoneCallback) => void
  | BullQueueAdvancedProcessor // { concurrency?: number; name?: string; callback: BullQueueProcessorCallback; }
  | BullQueueSeparateProcessor // string
  | BullQueueAdvancedSeparateProcessor; // { concurrency?: number; name?: string; path: string; }

to

export type BullQueueProcessor =
  BullQueueSeparateProcessor // string
  | BullQueueAdvancedSeparateProcessor; // { concurrency?: number; name?: string; path: string; }

@igor-sky there's already an example in the README. Doesn't this work for you?

from bull.

@fwoelffel Before removing processors property, please, provide an example, how to run job handlers in separate processes (using file name) with decorators approach

from bull.

@fwoelffel Is example available anywhere? Completely stuck on this one, can't sell nest-bull to lead without showing how to use workers in separate process :(

from bull.

Closed by 1dd0303

from bull.