-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silent error when injecatble requires itself #2481
Comments
It's not, there is actually no reason to support this feature. What would you like to accomplish? |
Nothing. I did this by mistake and was quite surprised how outcome looks like. When I figured out, I thought error should be thrown. |
Got it. Thanks for reporting! :) Fixed in 6.4.0 |
Cool, thanks! |
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. |
Bug Report
Current behavior
Nest allows injecting service to the same service (recursion happens?).
No errors are printed
Calling any endpoint returns
Error: Couldn't connect to server
Input Code
constructor(private service: AppService) {}
to AppServiceExpected behavior
Nest console should throw error
Possible Solution
Nest console should throw error
Environment
Is injecting service to itself valid operation?
The text was updated successfully, but these errors were encountered: