[Question] Is there a reason why Job.id is marked as optional in type definitions?

[BOTKooper]

I need to sync my db with bull a bit to track jobs, but while doing that i noticed that Job.id is marked as optional in both typescript definitions as well as at official docs.

Is that a bug in documentation, or there is a edge-case when worker can actually get a job without one?

I can see that it actually doesn't have one before scheduler creates it, but that coming into Worker type-def sounds a bit silly

P.S. not a dealbraker or anything - I still can pass it as part of the Job.data in my case, just a bit unexpected

[manast]

The reason is that a job does not get an id until it is stored in Redis... maybe there were more elegant ways to design this API, but I think it is difficult to change it now without a breaking change.

[BOTKooper]

That's reasonable, though I do not know if bullmq can skip redis when giving job to worker (which would be surprising to say the least).

If that's not the case - maybe we can make it smth like JobWithId inside Processor params? Shouldn't be a breaking change, but rather a clarification

[manast]

I think in that case what we can do is add a type guard to the process function where we know the id is present:
Job & { id: string }