Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Dapr.Configuration into separate client #1489

Open
WhitWaldo opened this issue Mar 17, 2025 · 2 comments
Open

Migrate Dapr.Configuration into separate client #1489

WhitWaldo opened this issue Mar 17, 2025 · 2 comments

Comments

@WhitWaldo
Copy link
Contributor

WhitWaldo commented Mar 17, 2025

Implementation for work described in #1427

With 1.16, we'll create a new client and run both the version in Dapr.Client and the separate package in parallel. Mark the affected methods in Dapr.Client with an [Obsolete("Use the Dapr.Configuration NuGet package instead as this method will be removed from Dapr.Client in v1.17")].

Do note that once I merge this PR, we'll be replacing the use of the [Obsolete] attribute with [Experimental] going forward.

@WhitWaldo
Copy link
Contributor Author

@siri-varma Assuming you're still free to take on this work, could you please use an "/assign" here for tracking?

@WhitWaldo WhitWaldo changed the title Move Dapr.Configuration into separate client Migrate Dapr.Configuration into separate client Mar 17, 2025
@WhitWaldo
Copy link
Contributor Author

@siri-varma Please note that I changed how each of the external client packages are expected to handle extension method DI registration in this PR. Make sure you're synced on branch "release-1.16" and make sure your DI extension method follows the example here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant