feature(core) property based injection (composition)

[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: #1014

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 1191

• 53 of 62 (85.48%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.4%) to 93.123%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/common/decorators/core/optional.decorator.ts	8	10	80.0%
packages/core/injector/module.ts	1	4	25.0%
packages/core/injector/injector.ts	28	32	87.5%

Totals
Change from base Build 1179:	-0.4%
Covered Lines:	2690
Relevant Lines:	2825

---

💛 - Coveralls

[BrunnerLivio]

Great job!
To clarify; this does not feature the proposed @Composition from #1014 property injection à la "inheritance-only-property-injection" / (similar like @Autowired in Spring), but a general "property-injection" right?

[kamilmysliwiec]

Yes @BrunnerLivio :) (still recommended to use constructor injection instead)

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