Named processors

[ejhayes]

I'm submitting a...

[x] Regression 
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

If using this library and you have:

@Process({
  name: 'NAMED_JOB_1',
  concurrency: 5,
})
async processSomeJob1(job: Job<any>): Promise<void> {
  // logic here
}

@Process({
  name: 'NAMED_JOB_2',
  concurrency: 5,
})
async processSomeJob2(job: Job<any>): Promise<void> {
  // logic here
}

Then both functions will get called regardless of the job name passed in.

Expected behavior

Specifying a named job should result in the correct processor being used. This functionality currently exists with the nestjs/bull package.

Minimal reproduction of the problem with instructions

The following should work:

@Process({
  name: 'A_NAMED_JOB',
  concurrency: 5,
})
async processSomeJob(job: Job<any>): Promise<void> {
  // logic here
}

What is the motivation / use case for changing the behavior?

Making this work would help ensure that this library remains a drop in replacement for the nestjs/bull package.
taskforcesh/bullmq#448 (comment)

Functionality wise, Bullv3 and BullMQ provides the same, it just that the syntax is different. In BullMQ you only define 1 processor, and then inside the processor you can choose different code paths depending on the "job.name" property. In your case this will mean a bit more of code, but named processors where causing a lot of confusion so we decided to remove the syntax sugar and made it more explicit.

Environment

For Tooling issues:
- Node version: 12
- Platform:  Mac

[brianschardt]

Any updates on when this will be fixed? or looked at?

[ejhayes]

@brianschardt might be a couple weeks until I have bandwidth for this. Seems like it should be an easy fix though. PRs welcome!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has bee marked as stale for too long. If you feel like it has not and should still be resolved, feel free to comment.

[bilalshaikh42]

Hi,
Is this something that you plan on working on?