Is It Possible to Expose Request/Response Types for Service Method Definitions

[kudla]

Hi @thesayyn!
While using directly loadSync from @grpc/proto-loader (comparing to protoc-gen-ts) it populates a service description additionally with requestType and responseType definitions. E.g.

{
  ServiceName: {
    MethodName: {
      path: '/ServiceName/MethodName',
      requestStream: false,
      responseStream: false,
      requestSerialize: [Function: serialize],
      requestDeserialize: [Function: deserialize],
      responseSerialize: [Function: serialize],
      responseDeserialize: [Function: deserialize],
      originalName: 'methodName',
//--------------------------------------
      requestType: [Object],
      responseType: [Object]
//--------------------------------------
    },
}

Is it possible to achieve the same with the protoc-gen-ts it self. Because for now the only solution I can see is just to abuse UnimplementedServiceNameService.definitiion and to inject it there manually. Or just to export full definitions separately.

Or is there any more pure designed solutions to have these definition within protoc-gen-ts classes?

I'm not really sure whether my huck solution will work at all since a final Client class extended from grpc_1.makeGenericClientConstructor( already wrapped the definition once I've been imported it. I'l take a try.

Thx.

[thesayyn]

Hmm, this looks like a new property introduced in a newer version of @grpc/grpc-js. I'd be happy to take contribution.