Since there's a new Jobs API showing up in Dapr in the near future, it should receive support in the .NET client.
As I'm actively advocating for the split out of Dapr client functionality into separate assemblies so that developers can explicitly opt-into those pieces of Dapr they're looking to use and so we can avoid some method naming conflicts (especially once I start hammering out the various specialty state APIs), I thought this would be an excellent place to start as it's quite a lightweight API footprint so far.
WhitWaldo
commented
4 months ago
Describe the feature
Since there's a new Jobs API showing up in Dapr in the near future, it should receive support in the .NET client.
As I'm actively advocating for the split out of Dapr client functionality into separate assemblies so that developers can explicitly opt-into those pieces of Dapr they're looking to use and so we can avoid some method naming conflicts (especially once I start hammering out the various specialty state APIs), I thought this would be an excellent place to start as it's quite a lightweight API footprint so far.
Release Note
RELEASE NOTE: ADD Support for Dapr Jobs API