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

Deprecating Aspire.Hosting.Dapr #7198

Merged
merged 4 commits into from
Jan 23, 2025

Conversation

aaronpowell
Copy link
Contributor

Closes #7049

This PR deprecates the Aspire.Hosting.Dapr package in favor of the Community Toolkit version (PR tracking its merge is here: CommunityToolkit/Aspire#408).

Removed the test project as it's not needed (code migrated to the Toolkit) and marked all members of the project with Obsolete (but not set as error to give people a release to upgrade).

@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Jan 22, 2025
@davidfowl
Copy link
Member

davidfowl commented Jan 22, 2025

On to a better home!

cc @IEvangelist

@davidfowl
Copy link
Member

@aaronpowell are you going to move the dapr issues?

@@ -1,12 +0,0 @@
<Project Sdk="Microsoft.NET.Sdk">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm good with removing the dapr playground app, but I wonder if removing the tests is a good idea. We are still building/shipping the code, it feels like we should still run the tests for it until we remove the code completely.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your call - I can revert that commit. The reason that I deleted them was to make it very clear in the code that this is unsupport.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests a pretty minimal.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it probably doesn't matter much either way. Just as a pattern it feels weird to delete the tests, but keep the code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like I said, your call and I can reinstate them if you'd be more comfortable.

@@ -21,6 +21,7 @@ public static class IDistributedApplicationBuilderExtensions
/// <param name="builder">The distributed application builder instance.</param>
/// <param name="configure">Callback to configure dapr options.</param>
/// <returns>The distributed application builder instance.</returns>
[Obsolete("The Dapr integration has been migrated to the Community Toolkit. Please use the CommunityToolkit.Aspire.Hosting.Dapr integration.", error: false)]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For my learning, does putting the Obsolete attribute on the whole static class not work? Or is it something wth extension methods that forces us to put it on each individual method?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You know... I didn't try 🤣

@aaronpowell
Copy link
Contributor Author

@aaronpowell are you going to move the dapr issues?

I don't think we can directly migrate the issues since it's cross orgs on GitHub.

@davidfowl davidfowl merged commit fc59d20 into dotnet:main Jan 23, 2025
9 checks passed
@davidfowl
Copy link
Member

Let's see what we need the follow up steps to be. @IEvangelist , @alistairmatthews we're moving dapr to the community toolkit, I know we just rewrote those docs!

@aaronpowell aaronpowell deleted the aaronpowell/issue-7049 branch January 23, 2025 02:47
@alistairmatthews
Copy link

Let's see what we need the follow up steps to be. @IEvangelist , @alistairmatthews we're moving dapr to the community toolkit, I know we just rewrote those docs!

We did. There is a /docs folder in the community toolkit. Maybe they could use our updated dapr.md?

@IEvangelist
Copy link
Member

Let's see what we need the follow up steps to be. @IEvangelist , @alistairmatthews we're moving dapr to the community toolkit, I know we just rewrote those docs!

We did. There is a /docs folder in the community toolkit. Maybe they could use our updated dapr.md?

@davidfowl is the NuGet packages changing at all? Does the community toolkit have access to the Aspire.* prefix, is that prefix reserved? We could move this recently rewritten doc under the Community Toolkit section in the TOC, @alistairmatthews - that should be easy.

@davidfowl
Copy link
Member

@IEvangelist yes it is changing CommunityToolkit/Aspire#408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate Aspire.Hosting.Dapr to the Community Toolkit
5 participants