Jeongho Nam

Of course why not?

If hope to avoid breaking change, I think NestJS guide document must warn the memory problem, and give an example code converting to the streaming strategy.

I'd tried to make concise `@UploadFile()` similar decorator supports both `express` and `fastify`, and understood why @kamilmysliwiec and @jmcdo29 had configured of `@UploadFile()` to just utilize the full `Buffer` data...

@VinayaSathyanarayana Use `typia`'s JSON schema generation function to the `@prisma/client` types. I think this is the fatest way at now. https://typia.io/docs/json/schema/

https://nestia.io/docs/sdk/sdk/#configuration @hmmhmmhm, @TheYarin Upgrade to v2.3, then you can do it. ```typescript import { INestiaConfig } from "@nestia/sdk"; import { Module, VersioningType } from "@nestjs/common"; import { NestFactory } from...

Not supported, and no way to support it.

validation and random data generation are fully completed: - validation through `@nestia/core` - random data generation through `typia.random()`

File uploading is related to frontend components. However, `@nestia/sdk` supports both NodeJS and Web browsers. Considering such aspects, I don't have clear idea. If you have a good interface design...

Now no problem through update of `typia`.

Have forgotten this issue for a long time due to busy. @Shandur Thanks for reminding. It's okay you to contribute eariler.