Closed mannharleen closed 2 years ago
@mannharleen hello. unfortunately, i don't use bullmq in production, so this one is not my highest priority atm. PRs are welcome, though!
do you reckon that the changes would mostly involve creating another class for BullMQ and implementing all that is here - https://github.com/s-r-x/bull-monitor/blob/main/packages/root/src/gql/data-sources/bull/index.ts
@mannharleen, don't think so. the main problem is that there is no abstraction over Queue class, and it is used as it is all over the place. For example, there is the text search class, that heavily relies on bull internals. One way to solve it is to wrap user defined queues in some kind of adapter. Otherwise if bull and bullmq apis are quite similar i guess you can patch the differences here and there using instanceof. Anyways bullqueue type should be changed everywhere from bullqueue to somequeueadapter in the first case, and to bullqueue | bullmqqueue in the second one. Which is helluva refactor
Understand. That sounds like a lot of rework 🤔
@mannharleen what specifically are you looking for ? I imagine you've looked at bull-board
which supports bullmq
. Is there something missing in bull-board
as well ?
added in 3.0.0
Thanks mate
Is there a plan to support bullmq?