David Aktary

_PLEASE_ do this. It's a must for hybrid developers!

We're having the same problem with the `@kubernetes/client-node` package. We tried using the `ignore` config so Tsoa wouldn't crawl the `node_modules` folder, but it doesn't seem to respect that config...

ok... checking back in with an update. We had complexity because we're running a monorepo that I won't get into here, but this setting in `tsconfig.json` worked to get tsoa...

It shouldn't be discovering anything in `node_modules`, should it? I can say for sure in our case that we don't want anything in `node_modules` exposed.

Yes, I agree that if we expose it via an interface, it should be included, but that's not the case here. One of my developers had this happen with the...

Gaaah! Of course. Yes, after making that modification, it works. However, fat arrow declarations are pretty common and popular now. Why not support them? I recognize this changes this issue...

> E: If you don't mind I'd like to change the title to something like: "Functions declared as Property Declarations in Controllers are not considered for Route/Metadata generation" so other...

Ok... update. I've figured out that I can follow the examples for useGet() (and, presumably useMutuate()) and they'll generally apply to my generated hooks. Closing for now.

Yeah... I'm still lost. Is it possible to use the generated code outside of a tsx context? If I've got a simple TS module that does some network requests, can...

We'd really like to see this implemented, but I can see this issue is quite old. Is it going to happen?