Yaron Schneider

> I finished up the node and python examples. https://github.com/patrickhuber/components-contrib/tree/master/state/plugin/fixtures/state/ Hey Patrick, this will be discussed in tomorrow's community call. It'd be great if you could participate.

> I will write down the details in the existing issue: #814 Thanks @ItalyPaleAle. We encourage setting expectations before submitting a PR as laid out in our [contributions guide](https://github.com/dapr/dapr/blob/master/CONTRIBUTING.md#pull-requests).

cc @beiwei30 @daixiang0 @cvictory @msfussell @Forrest-zhao @paulyuk

> the Dapr WF engine's semantics will become a pseudo-standard The goal is to make the Dapr WF APIs (and all Dapr APIs in general) a standard and via [work...

> Indeed, it's a deviation from how other Dapr building blocks work Not much of a deviation. The Configuration API started out as gRPC only, and the upcoming Distributed Lock...

> The API surfaces for the building blocks are simple hence why you can bring your own HTTP or GRPC client (and avoid using SDKs) but with the workflow SDK...

> Got it. I forget that dapr Actors require an SDK for the programming model. In that case, ignore everything I’ve said! No, you did bring up a valid point....

The second approach is much preferable to the first. Reference fields in CRDs referencing other Kubernetes objects are a common design and I am not at all worried about the...

> Runtime error in this case means shutting down the sidecar? Yes. It's a valid reason to panic. > So the enduser can't use them together because of the naming...

> Does it makes sense to you ? Not very much, no :) > if we add more attributes in the pluggable component this needs to be repeated in each...