Valentin Marchaud

> the API looks similar though - it might have been nicer to contribute to tsoa instead. `tsoa` isn't the same implementation as `typoa`, i don't think it would have...

I'm not sure this is an actual problem end user will face, having different `TracerProvider` is theorically possible and is required by the spec (i believe), however there were questions...

I'll go ahead ang move this issue to the core repo seems the instrumentation will most likely go there

Indeed that make sense, feel free to open a PR i'll review it

@brillout I'm interested into understanding what's your requirement for having to host meilisearch (or any database) to the edge ? Is that a latency requirement ? Maybe easier deployment ?...

We should add a option to be able to declare dependencies between app like docker-compose do.

I mean we could lookup in the TS compiler where each controller / endpoint is defined to add a description into the specs on which file contains the implementation ?

> the spec would just point them to a file like ./src/controllers/User.controller.ts? Yeah i think we can extract the lines of where a specific struct is defined from TS ?

Wondering if we could append it directly inside the description ? Could be a flag to not be the default

We currently automatically add the comment if present on controller https://github.com/Eywek/typoa/blob/0c607b107afc04e5c6b9585f9d2439c0c489eb55/src/controller.ts#L40 or using jsdoc https://github.com/Eywek/typoa/blob/0c607b107afc04e5c6b9585f9d2439c0c489eb55/src/resolve.ts#L580 Adding a decorator should be pretty straightforward if you want to make a PR