feat(validated-non-primitive-property-needs-type-decorator): allow additional options for custom validator decorators to detect

[austinwoon]

Context

I have some custom class-validator decorators that I would like to enforce this rule on. Currently, we detect if an import is a class-validator import by detecting if the import is from class-validator. This prevents the rule from being enforced when custom validators are applied.

Proposed solutions

• Extend the available options to include an additional param customClassValidatorDecorators which will take in a list of decorator names to check. This is a simple string match check, but has the con of naming collisions if for whatever reason we have other decorators of the same name within the project not meant for validation. It is also consistent with the current additionalTypeDecorators options api.
• Extend available options to take in a list of file paths for imports to check against. This file path will contain all the custom decorators we wrote. Con: This prevents naming collisions, and will not require us to update the decorator names whenever we add new decorators to the project.

[darraghoriordan]

:tada: This issue has been resolved in version 3.18.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: