Ashleigh Simonelli

No I've not seen that? Tbh the amqplib library is awful in terms of naming etc. Least its consistent between languages lol I'll have a look into it :) luckily...

This issue is because the connection provider is created 'dynamically' when the module's forRootAsync is called. So the provider is created by awaiting an amqp connection and then the provider...

Sorry I did start writing a reply but been mega busy! I'll try and make you an example repo and play around with it. I'm going on holiday tomorrow night...

Sorry I didn't forget just been mega busy! So I tried replicating your code into a test, I updated my nest modules to the latest of latest and I get...

Sorry it's been ages... Been mega stressed :joy: isn't life great! So I've taken a quick look and there was only one issues causing the v6 to not pass tests...

@probil I've just had a thought. You are running `await app.init();` right? Because the amqp providers are created in `onModuleInit()`. @jmcdo29 yea sure I've thought about doing the same thing...

Hey @ruslanguns! Someone has already built an interceptor for this package! However I've been absolutely abysmal at keeping up to date with everything the past 2 years! #18 However getting...

Ahhhh yes, sorry, misunderstood. So, if you're using typeorm you could use a subscriber to update your roleBuilder's roles but that wouldn't invoke a change when the DB is updated...

@ruslanguns don't suppose you've got a stack trace?

I think your inject token is incorrect? Try this ``` AccessControlModule.forRootAsync({ inject: [ROLE_REPO], useFactory: (service: Role) => { return new RolesBuilder([ ...adminGrants // testing local file grants ]); }, }),...