gRPC server currently doesn't support client-side streaming

[lhr0909]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Currently the gRPC server implementation, the call.request is being passed in, however, for client-side streaming (and bi-directional streaming), there isn't request field in the call, but rather call itself is a readable stream on its own.

Reference:

in grpc-node package:
https://github.com/grpc/grpc-node/blob/master/packages/grpc-native-core/index.d.ts#L385
https://github.com/grpc/grpc-node/blob/master/packages/grpc-native-core/index.d.ts#L462

in nestjs-microservices package:
https://github.com/nestjs/nest/blob/master/packages/microservices/server/server-grpc.ts#L134
https://github.com/nestjs/nest/blob/master/packages/microservices/server/server-grpc.ts#L144

Expected behavior

NestJS handlers should be able to detect whether or not the grpc call has client-side streaming, and pass call directly.

Minimal reproduction of the problem with instructions

N/A

What is the motivation / use case for changing the behavior?

We are already doing great work encapsulating gRPC microservices, it would be cool to have full client-side streaming support. I am not sure if we should go full-on observable style for processing the client-side streaming calls, but I am all for it since I am in love with Rx and NestJS is already converting server-side streaming handshake to use observables.

Environment

Nest version: 5.x, 6.x

 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[lhr0909]

Oops, I should really look at #1568 first, closing this for now.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.