feature(common): add option to allow validation of custom decorators

[TheNoim]

No matter what the reason is to not validate custom decorators, you should be able to at least provide an option

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: #2010

You are required to create a new validation pipe for custom decorators. You cannot use the build in one.

What is the new behavior?

You have the option to allow the validation of custom decorators.

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[kamilmysliwiec]

Great, thanks! Would you like to add a PR to the docs as well? (see options table https://docs.nestjs.com/pipes#the-built-in-validationpipe)

[coveralls]

Pull Request Test Coverage Report for Build 3038

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.001%) to 95.247%

---

Totals
Change from base Build 3034:	0.001%
Covered Lines:	3427
Relevant Lines:	3598

---

💛 - Coveralls

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