Use another proto-loader for grpc

[grin0c]

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

Cannot use another proto-loader instead of @grpc/proto-loader

Expected behavior

You will be able to use another proto-loader

Some of the major changes:

export class ServerGrpc extends Server implements CustomTransportStrategy {
  private readonly url: string;
  private grpcClient: any;

  constructor(private readonly options: MicroserviceOptions['options']) {
    super();
    this.url =
      this.getOptionsProp<GrpcOptions>(options, 'url') || GRPC_DEFAULT_URL;

    const protoLoader =
      this.getOptionsProp<GrpcOptions>(options, 'protoLoader') || GRPC_DEFAULT_PROTO_LOADER;

    grpcPackage = this.loadPackage('grpc', ServerGrpc.name);
    grpcProtoLoaderPackage = this.loadPackage(
      protoLoader,
      ServerGrpc.name,
    );
  }

Minimal reproduction of the problem with instructions

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

I want to use grpc without protocol buffers and I want to use another serialization/deserialization

Environment

Nest version: 5.4.0

 
For Tooling issues:
- Node version: 8.12.0  
- Platform: Mac  

Others:

[kamilmysliwiec]

5.5.0 has just been published :)

[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.