Currently there's no way to do this using the current grpc-web code generator - it will generate for all messages and methods. I am not aware of any canonical way of marking messages and methods public or private as protobuf syntax.
On Sunday, February 16, 2020 at 8:14:55 AM UTC-8 [email protected] wrote: > Hey > We are currently using grpc for internal communication between > microservices. > We would like to use grpc with grpc-web for FE to BE communication. > Whats the best way to do this without exposing internal data structures > that we don't want to be seen by analyzing the generated java script files > on the client side? > Ideally we would want to mark "external" messages/service rpc methods and > have only those exposed. > Thanks in advance. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5dca043f-f2ac-4b1e-a495-ad23bd1c96c4%40googlegroups.com.
