"custom options" exist, but frankly they don't do much unless you have custom code generation that is going to emit something useful from them, and that "something" itself does something useful at runtime - which may itself be tricky between runtimes/platforms.
Does "add a comment" suffice? On Wed, 14 Oct 2020 at 08:43, Guy Pardon <[email protected]> wrote: > Hi, > > Being new to protocol buffers and gRPC, I am looking for a good way to add > metadata "annotations" to the contract description. > > In particular, we are adding transaction context propagation across gRPC > calls. We would like to mark some RPCs (or services) as "transactional" - > meaning that they expect / support a transaction context header in the > incoming request. > > What is the recommended way of doing this? I did not seem to find this in > the documentation. > > Thanks, > Guy > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" 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/protobuf/fdbe28a3-56de-4958-b138-ca4c2e6fb896n%40googlegroups.com > <https://groups.google.com/d/msgid/protobuf/fdbe28a3-56de-4958-b138-ca4c2e6fb896n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Regards, Marc -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" 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/protobuf/CAF95VAy7C%3DGXrewhSjB1-W%2BiFXV7Xrf6JBzFZmyqbKyrjX7byQ%40mail.gmail.com.
