Adriano Santos

> The issue is not related to TCK testing features so it should not impact anyone using this library. but I still sent a PR https://github.com/nagytech/cloudstate-csharp/pull/7

The silence....

Thanks @jboner for answering. Good luck in your business.

Maybe we should just delegate the headers via proxy to the user space. Implementers could access these headers via Context like this pseudo kotlin code: ``` @CommandHandler fun getCart(ctx: CommandContext):...

Of course we could allow annotations on the protobuf to enable or disable this feature or allow filters for which headers we are interested in having access to. I think...

Hi @marcellanz I believe that if there is no note in proto that indicates which headers should pass, then all headers should pass, otherwise only the headers specified in the...

@viktorklang @marcellanz ping

"I'd be fine with defining a set of supported headers and semantics for how they are to be interpreted by the proxy" - I'm not sure if I was able...

Remembering that the proto definition would be an exception not in the rule. Seen everything I said above

"It would be good to come up with some canonical use-cases that we can use to drive the development of this feature forward. Wdyt?" - Looks good!