How to avoid duplicity taxation between input and output DTO blocks in SonarQube?

Dear all, I’m facing a critical issue in our project, which is having a major impact on the pipeline. The problem occurs when there is duplicity between an input DTO block and an output DTO block, resulting in duplicity taxation. I would like to know what would be the best practice to avoid this situation?

Hi,

Welcome to the community!

If it’s not feasible to eliminate the duplication, you may just need to set an exclusion.

 
HTH,
Ann