halspang

@peter-alegeus - Thanks for opening this issue! Everything should be mockable as all of the non-abstract methods in the DaprClient actually call down to the abstract ones. I think the...

We have no plans to add an interface for `DaprClient`. One thing we can do is add `virtual` to all the client methods. This would allow them all to get...

> Hey being able to mock is a strong reason.. just saying.. a very strong reason in my point of view. @DexManx - It is a strong reason, but as...

Pretty sure this is happening in here: https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Actors/Builder/ActorCodeBuilder.cs I think providing a better exception is probably the right path here. Maybe my understanding of the scoping is incorrect but I...

@bcraun - Thanks for opening this! Can you fix your command for Step 1.? I want to make sure I'm trying to reproduce this correctly.

@bcraun - I haven't had a chance to repro it yet, hoping I can get to it soon.

@yaron2 - prefer the language here, but this is technically a breaking change. Syncing with @rynowak on what our process here is since this is an Alpha API.

@wjkhappy14 - You can also start dapr separately from your app as it will wait for your app port to start listening to finish starting. You can then debug your...

We'll add a new method that will skip the json serialization portion and work on raw bytes instead.

@mukundansundar - I like the idea of it being a subcommand instead of a top-level like `dapr resiliency`. If we're moving towards having a `dapr resources` I think having it...