feature(core): Add module context name to UnknownDependenciesMessage

[BrunnerLivio]

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?

The error when a injection dependency is missing does not show from which Module it is talking about

Issue Number: N/A

What is the new behavior?

It tries to parse the current module context name and shows the error message (note the CatsModule in the message):

[Nest] 20205   - 2018-10-2 11:56:51   [ExceptionHandler] Nest can't resolve dependencies of the CatsController (?). Please make sure that the argument at index [0] is available in the CatsModule context. +27ms

In case the module name can not be parsed somehow, it will use the string 'current' as fallback name for the module, as it used to be.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

[coveralls]

Coverage remained the same at 93.67% when pulling 4e943db on BrunnerLivio:feature/print-context-injection-error into 65bb7e7 on nestjs:master.

[kamilmysliwiec]

Great job 💪

[anodynos]

Any chance to merge & publish this PR? I'm facing a #861 :-(

[BrunnerLivio]

Is there anything blocking or can this be merged into the 5.4.0 branch? @kamilmysliwiec

[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.