Skip to content

Documentation needs to flag that this is not compatible with class-transformer #391

@acuthbert

Description

@acuthbert

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

I spend a frustrating few hours wondering why my Expose() decorator was not being honoured. I was using the @nestjs/class-transformer package which felt appropriate. However the ClassSerializerInterceptor class from @nestjs/common does not read this meta data store by default.

This is incongrous and has caused many members of my team to hit the same problem.

Describe the solution you'd like

The README needs to be clear why this package exists, and why is it better then class-transformer, but most importantly, how should it be enabled, and how to handle libraries that might use class-transformer decorators.

Teachability, documentation, adoption, migration strategy

No response

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

The motivation is simply to improve the developer experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions