Reusing redis connection for bull v4+, outdated doc?

[DavideViolante]

Description

Hello, I'd like to know if this doc is outdated because since bull v4 the breaking change says that these 2 redis options are now compulsory:

{
  maxRetriesPerRequest: null,
  enableReadyCheck: false
}

In the doc it just passes the REDIS_URL in the new Redis(). Does it need also the other 2 options?

Minimal, Working Test code to reproduce the issue.

(An easy to reproduce test case will dramatically decrease the resolution time.)

Bull version

4.12.2

Additional information

[manast]

I think you may be mixing Bull and BullMQ. The options you name are compulsory in BullMQ not in Bull.

[DavideViolante]

I'm quite confused. The doc I linked is bull, correct? bullmq is another repo?! The release notes and changelog are about this repo, not bullmq. The 4.0.0 breaking changes says, for bull:
If redis opts are missing: { maxRetriesPerRequest: null, enableReadyCheck: false } then a exception will be thrown.

[manast]

Ah ok, I forgot we also backported this requirement to Bull, sorry for the oversight. Most likely we will not update the docs as we are putting all our efforts on BullMQ these days though.

[DavideViolante]

I made a PR to update that file. I think it's totally safe to merge if the text is correct.