Skip to content

ProviderAliasAttribute moved to Microsoft.Extensions.Logging.Abstractions solution. #114606

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

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

SetTrend
Copy link
Contributor

resolves #114532

Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

1 similar comment
Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

…soft.Extensions.Logging.Abstractions` solution.
@SetTrend SetTrend force-pushed the ProviderAliasAttribute_Abstractions branch from 453a410 to ab6d4cb Compare April 14, 2025 16:37
@tarekgh tarekgh marked this pull request as ready for review April 14, 2025 16:52
@tarekgh tarekgh added breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. and removed new-api-needs-documentation labels Apr 14, 2025
@dotnet-policy-service dotnet-policy-service bot added the needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet label Apr 14, 2025
Copy link
Contributor

dotnet-policy-service bot commented Apr 14, 2025

Added needs-breaking-change-doc-created label because this PR has the breaking-change label.

When you commit this breaking change:

  1. Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the breaking change documentation template, then remove this needs-breaking-change-doc-created label.
  2. Ask a committer to mail the .NET Breaking Change Notification DL.

Tagging @dotnet/compat for awareness of the breaking change.

@tarekgh tarekgh removed the needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet label Apr 14, 2025
@tarekgh
Copy link
Member

tarekgh commented Apr 14, 2025

The breaking change doc issue dotnet/docs#45806 is filed.

@tarekgh
Copy link
Member

tarekgh commented Apr 14, 2025

/ba-g the build failure is unrelated

@tarekgh tarekgh merged commit b044b20 into dotnet:main Apr 14, 2025
87 of 91 checks passed
@tarekgh
Copy link
Member

tarekgh commented Apr 14, 2025

Thanks @SetTrend for providing the change.

@ericstj ericstj changed the title WIP: ProviderAliasAttribute moved to Microsoft.Extensions.Logging.Abstractions solution. ProviderAliasAttribute moved to Microsoft.Extensions.Logging.Abstractions solution. Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Extensions-Logging breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. 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.

[API Proposal]: ProviderAliasAttribute: Better move to Microsoft.Extensions.Logging.Abstractions
3 participants