Honestly, Linters are crazy, fixing them up.

Really I would admire, if linting check is not done at least on server for now.
What are your views @Abhishek-kumar09 :(
This is something making me feel not good

Did you tried running npm run lint:fix

Can you add this to your GitHub Actions ?
Let me create an issue for the same

@Abhishek-kumar09 I added few a command to let Workflow run, the npm run lint:fix
Let me know if you feel good about it.

I see, we are doing this to serialize the returned object.
It is being said in the documentation that

Nest detects when the handler is using either @res() or @Next(), indicating you have chosen the library-
specific option. If both approaches are used at the same time, the Standard approach is automatically disabled

Infact, we don't need library specific response here, I believe.
Instead we can use standard approach to return simple json object and the nest will handle everything automatically and it is recommended approach also.

Yes and thats why to maintain standard approach
passthrough:true is added

I meant removing @Res library fully to follow the standard approach and infact returning the json responses from nest.

We do need @Res for future cases. So cant remove it. @Abhishek-kumar09

We do need @Res for future cases. So cant remove it.

Not really, When we are using @Res we are just using or forcing to use express library response behaviour.

When we are returning the object using standard approach, we can omit the use of @Res.
I don't think if there will be some specific use case for @Res in the future.

Here is the example of removal of @Res and picking standard response controller provided by nestjs 2e30df8#r49621473.