add isController/ isService check util

I’m submitting a…

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

I didn’t find any way to check if a class is controller/service without referring to Nest internal values.

Expected behavior

I’d like Nest to provide exported functions to check if a class is decorated with Controller /Injectable.

Minimal reproduction of the problem with instructions

N/A

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

I am writing a tool to automatically load controllers& services from project directory. However, as Nest throws when loading non-Controller classes as controller, it requires to check if a class is Controller before gathering them into an array and pass to Module decorator.

Environment

Nest version: 5.4.0
 
For Tooling issues:
- Node version: v10.13.0
- Platform:  macOS

Others:

[marcus-sa]

Unless you’re creating a 3rd party library, you could just proxy/wrap the decorators and add metadata to them yourself to determine whether or not its a controller or service.

Anyhow you’re wrong, the @Controller() decorator does define metadata on the metatype.

https://github.com/nestjs/nest/blob/385071ba6dd3b98f91edfca0ed5aadb611bb678f/packages/common/decorators/core/controller.decorator.ts#L4-L13

I still don’t get what you want. Basically what you’re trying to accomplish is the exact opposite of what module architecture frameworks are here for. If you just glob through your entire project to put controllers and providers into the module decorator, then what’s the point of even using Nest?

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.