Durable provider scope wins over non durable.

[vizio360]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When using durable providers, if a service has 2 dependencies, one durable and the other still REQUEST scope but NON durable, the service inherits the REQUEST DURABLE scope.

Minimum reproduction code

https://github.com/vizio360/nestJSDurableProvidersIssue

Steps to reproduce

See reproduction code

Expected behavior

If there is at least one dependency with just REQUEST scope (non durable) the service should be REQUEST scope non durable as well.

REQUEST Scope non durable should win over REQUEST scope durable.

and I would expect the overall priority for scopes to be (high to low):

REQUEST non durable
REQUEST durable
DEFAULT

Package

• I don't know. Or some 3rd-party package
• @nestjs/common
• @nestjs/core
• @nestjs/microservices
• @nestjs/platform-express
• @nestjs/platform-fastify
• @nestjs/platform-socket.io
• @nestjs/platform-ws
• @nestjs/testing
• @nestjs/websockets
• Other (see below)

Other package

No response

NestJS version

9.2.0

Packages versions

[System Information]
OS Version     : macOS Monterey
NodeJS Version : v16.13.2
NPM Version    : 8.1.2 

[Nest CLI]
Nest CLI Version : 9.1.5 

[Nest Platform Information]
platform-express version : 9.2.0
schematics version       : 9.0.3
graphql version          : 10.1.6
testing version          : 9.2.0
apollo version           : 10.1.6
common version           : 9.2.0
core version             : 9.2.0
cli version              : 9.1.5

Node.js version

16.13.2

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

No response

[vizio360]

I've removed the TRANSIENT scope from the expected overall scope priority as it is a special case as explained in the docs: https://docs.nestjs.com/fundamentals/injection-scopes#scope-hierarchy

[kamilmysliwiec]

Let's track this here #10698