feat(core): add resolve method to load scoped classes

[kamilmysliwiec]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

resolve() method that allows loading both transient and request-scoped providers dynamically

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 3911

• 3 of 4 (75.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.02%) to 95.213%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/core/injector/module.ts	2	3	66.67%

Totals
Change from base Build 3905:	-0.02%
Covered Lines:	3640
Relevant Lines:	3823

---

💛 - Coveralls

[underfin]

let trace the issues #2049.Maybe should resolve scope provider.

@Module({
  imports: [],
  providers: [
    {
      scope: Scope.TRANSIENT,
      provide: 'TRANSIENT_PROVIDER',
      useFactory: () => {
        // Does not get called
        console.log('Called `TRANSIENT_PROVIDER`');
        return 'TRANSIENT_PROVIDER_VALUE';
      }
    },
  ]
})
export class AppModule {}

async function bootstrap() {
  const app = await NestFactory.createApplicationContext(AppModule);

  // Returns `null`
  app.get('TRANSIENT_PROVIDER')}
}

I meet error when test with this.

[kamilmysliwiec]

@underfin you should use await app.resolve() instead of .get() method

[ulrichb]

@kamilmysliwiec Is it possible to use this in tests to fake Request-scoped providers?

I would like to resolve services which depend on faked Request-scoped providers.

[kamilmysliwiec]

Yes @ulrichb. I'm working on the docs for this now

[ulrichb]

Okay, cool! Looking forward to this.

[aevartg]

@kamilmysliwiec, @ulrichb are the docs ready for this? cant seem to find them.

[xxluke]

@aevartg I think the docs for this will be written in nestjs/docs.nestjs.com#623

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.