You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current @nestia/sdk is using await import statement for every controller class ts files with ts-node. Therefore, @nestia/sdk is repeating TypeScript source parsing through TypeScript compiler API whenever new controller class comes, and such repeated process is making SDK library and Swagger Documents generation speed extremely slower.
To reduce the generation time, I'll abandon the await import statement with ts-node, and inject metadata information in the compilation level through transform API. Instead, this strategy requires @nestia/core must be required even when using only @nestia/sdk, but I think reducing generation time would be valuable for enduring the dependency.
The text was updated successfully, but these errors were encountered:
Thank you for answer, is it possible to make the generate method parallel when performing code analysis?
For example, in my NestJS project, there are 10 controllers. Wouldn't it be possible to analyze all 10 controllers simultaneously using a function like Promise.all?
Current
@nestia/sdk
is usingawait import
statement for every controller classts
files withts-node
. Therefore,@nestia/sdk
is repeating TypeScript source parsing through TypeScript compiler API whenever new controller class comes, and such repeated process is making SDK library and Swagger Documents generation speed extremely slower.To reduce the generation time, I'll abandon the
await import
statement withts-node
, and inject metadata information in the compilation level through transform API. Instead, this strategy requires@nestia/core
must be required even when using only@nestia/sdk
, but I think reducing generation time would be valuable for enduring the dependency.The text was updated successfully, but these errors were encountered: