There are a couple of method signatures in the generated TypeScript client that should mark the metadata parameter as optional, to reduce explicitly passing unnecessary null values:
Making the metadata parameter optional in the method returning a Promise would bring the TypeScript client closer in line with the PromiseClient interface available when generating with import_style=commonjs+dts.
This is an inverse issue to https://github.com/grpc/grpc-web/issues/408
There are a couple of method signatures in the generated TypeScript client that should mark the
metadataparameter as optional, to reduce explicitly passing unnecessarynullvalues:https://github.com/grpc/grpc-web/blob/0ec55aaad784e114bcb391b0b33ac4fd2e83e3f2/javascript/net/grpc/web/generator/grpc_generator.cc#L652-L655
https://github.com/grpc/grpc-web/blob/0ec55aaad784e114bcb391b0b33ac4fd2e83e3f2/javascript/net/grpc/web/generator/grpc_generator.cc#L670-L674
Making the
metadataparameter optional in the method returning aPromisewould bring the TypeScript client closer in line with thePromiseClientinterface available when generating withimport_style=commonjs+dts.