Support @Expose() and @Exclude() or allow custom @ApiHideProperty() decorators

[kurt-west]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

With the CLI plugin not supporting the class-transformer @Expose and @Exclude and @ApiHideProperty() not being composable the developer experience is less than it could be.

Describe the solution you'd like

The optimal - IMO - solution would be to add a class-transformer shim that scans for Expose like the class-validator shim does and extends the array of decorators (currently only ApiHideProperty) used to skip a property to include Exclude. I see this idea has been shutdown multiple times.

The other option would be to add a plugin configuration option hidePropertiesDecoratedWith that is an array of strings that will be ignored when the plugin is processing. The exclusion logic already exists (hidePropertyDecorator) and supports an array of strings. The plugin options are locally available in the method (visitPropertyNodeDeclaration) used to decide if a property is annotated or not.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

Using class-transformer for validation and serialization is at the core of NestJS it would be great to improve the DE so the swagger module is intergraded with these core concepts. Also, selfishly I'm sick of seeing @Exclude() and @ApiHideProperty side-by-side or missing @ApiHideProperty and the property being shown in the documentation.

I'm happy to do a PR to support either or both of these changes.

[kamilmysliwiec]

The optimal - IMO - solution would be to add a class-transformer shim that scans for Expose like the class-validator shim does and extends the array of decorators (currently only ApiHideProperty) used to skip a property to include Exclude. I see this idea has been shutdown multiple times.

Would you like to create a PR for this issue?

[kurt-west]

The optimal - IMO - solution would be to add a class-transformer shim that scans for Expose like the class-validator shim does and extends the array of decorators (currently only ApiHideProperty) used to skip a property to include Exclude. I see this idea has been shutdown multiple times.

Would you like to create a PR for this issue?

I definitely can and will, thank you.

[mateussaggin]

This is indeed extremely necessary.
@kurt-west did you have the opportunity to take a look and crate the PR?