Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add ability to set grpc-js MetadataOptions when using GrpcTransport
See original GitHub issueWhen grpc-js calls are made, it’s possible to set Metadata, which besides key-value pairs, also contains a few pre-defined options set in constructor with MetadataOptions object ).
Currently the generated rpc clients in protobuf-ts take RpcOptions object, which contains meta: RpcMetadata, but this option doesn’t seem to support populating the same options as in MetadataOptions when call is made using GrpcTransport.
I suppose GrpcMetadata object could be added to grpc-transport package, which would extend RpcMetadata and calls using grpc transport could translate them to fully populate Metadata. I’m not sure if this translation could be done in a type-safe way - this would probably require baking in some extensibility into generic client.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
grpcweb-transportdoesn’t usegrpc-js, so it doesn’t consume itsMetadataOptions. One could imagine some of the functionalities from those options to be implemented ingrpcweb-transport, but that is an independent feature.Does grpcweb-transport affected by the same issue?