Dependencies cannot be resolved when using forRootAsync about bull

[mayorandrew]

Based on https://github.com/fwoelffel/nest-bull/blob/master/lib/bull.providers.ts#L39 it looks like that you should have name property defined outside of the useFactory, like this:

@Module({
  imports: [
    ConfigModule,
    BullModule.forRootAsync({
      imports: [ConfigModule],
      name: 'slack-announce',
      useFactory: (configService: ConfigService) => ({
        options: {
          redis: {
            port: 6379,
          },
        },
      }),
      inject: [ConfigService],
    }),
  ],
  providers: [SlackAnnounceRankingProcessor],
  controllers: [],
})
export class SlackModule {}

This works. It doesn't seem quite right though...

[fwoelffel]

Hi @joshuajung 👋
I've look into the code and I'm affraid it won't be possible to define the queue name from the useFactory. If you take a look at https://github.com/fwoelffel/nest-bull/blob/master/lib/bull.providers.ts#L46 (or https://github.com/fwoelffel/nest-bull/blob/13-async-array-configuration/lib/bull.providers.ts#L45 which will soon be merged into master) you can see by your self that I need the queue name to build the injection token. Thus, I can't wait for the result of the useFactory function.
If you have an idea on how to do this, feel free to submit a PR 🙂

[fwoelffel]

@joshuajung Sorry I didn't have quite the time to investigate on this issue yet. Could you confirm that @mayorandrew's answer is fixing your issue?

@mayorandrew yup, you're right, I don't know why I implemented this non-sense. Sorry for that, I'll try to deprecate this and provide a non-breaking solution to this. Thanks for taking some of your time to have a look on this.

[joshuajung]

@fwoelffel Happy to confirm this did the trick!
@mayorandrew Thanks a lot for your effort! I would have never found that myself.

[fwoelffel]

Awesome, thanks for your feedback. I feel like I should add a forRootAsync example in the README.
I'm closing this.

[joshuajung]

Hey @fwoelffel, Thanks a lot for taking the time and looking into it! Now that I know that name is defined outside useFactory, that's perfectly fine for me. Unfortunately, my skills won't suffice for making a meaningful contribution here. Thanks again!

[JVMartin]

Just ran into this now in 2020.

The docs do not detail this at all:
https://docs.nestjs.com/techniques/queues

Would someone with the appropriate power be able to update the docs to include a name property in the proper location in the .registerQueueAsync section? This would have taken me many hours to figure out without this thread.

[kamilmysliwiec]

@JVMartin I've just pushed an update to the docs. Thanks!

[investeusa]

@JVMartin Acabei de enviar uma atualização aos documentos. Obrigado!

Did you test this? The documentation is not clear to those who are starting.

I have the same problem.

**queues.config.module.ts**

@Module({
    imports: [
        BullModule.forRootAsync({
            imports: [ConfigModule],
            inject: [ConfigService],
            useFactory: async (configService: ConfigService) => ({
                redis: {
                    host: configService.get('REDIS_HOST'),
                    port: configService.get('REDIS_PORT'),
                },
            }),
        }),
        QuotesQueueModule
    ]
})
export class QueuesModule {}

**queues.service.ts**

@Injectable()
class BullConfigService implements BullOptionsFactory {
  createBullOptions(): BullModuleOptions {
    return {
      redis: {
        host: 'localhost',
        port: 6379,
      },
    };
  }
}

**error:**

(node:261) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 0.0.0.0:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1129:14)
(node:261) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

[kamilmysliwiec]

Please, use our Discord channel (support) for such questions. We are using GitHub to track bugs, feature requests, and potential improvements.