Jeongho Nam

I don't have insight about this subject. Can you explain me more detaily? > In my case, when websocket being required, I used this library instead. > > https://tgrid.com/en

It is possible to support swagger examples. By the way, do you think that the examples should be put into the SDK?

```typescript /** * Store an article. * * @param input Content to store * @returns Newly archived article * @deprecated * * @controller BbsArticlesController.store * @path POST /bbs/articles * @nestia...

I will check the propagate type again. By the way, how to write the example data in the method? Do you have any idea?

As I also have to consider the fastify case, supporting express-multer options are not easy problem. Will you suggest or send a PR that can make both express and fastify...

Seems good. What about challenge a PR in here code? https://github.com/samchon/nestia/blob/master/packages/core/src/decorators/TypedFormData.ts

Your suggestion is a typical anti pattern that violating standard. If you write a query string `"person.address.id=2`", it means `obj["person.address.id"] = 2` in the query string spec. Also, URL path...

Instead, I recommend to use request body of POST/PATCH/PUT/DELETE methods. The request body does not have any length and depth limit. In my case, I prefer `PATCH` method when replacing...

In that case, it would better to use `@Query()` of original NestJS. Also, in that case, how serialize the query string in the frontend application? I need to update the...

Oh my god, looking at the format option, it seems terrible and why could not be standard. Have you to use it? It seems not easy to support from SDK...