-
Notifications
You must be signed in to change notification settings - Fork 5k
Update new LoggerMessage.Define
APIs, to take LogDefineOptions
#54581
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
Conversation
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to 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. |
Tagging subscribers to this area: @maryamariyan Issue DetailsChange API for the new Contributes to #50913
|
src/libraries/Microsoft.Extensions.Logging.Abstractions/src/LogDefineOptions.cs
Outdated
Show resolved
Hide resolved
src/libraries/Microsoft.Extensions.Logging.Abstractions/src/LoggerMessage.cs
Outdated
Show resolved
Hide resolved
src/libraries/Microsoft.Extensions.Logging.Abstractions/src/LoggerMessage.cs
Outdated
Show resolved
Hide resolved
LoggerMessage.Define
APIs, to take LogDefineOptionsLoggerMessage.Define
APIs, to take LogDefineOptions
LoggerMessage.Define
APIs, to take LogDefineOptions
LoggerMessage.Define
APIs, to take LogDefineOptions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is gonna be a breaking change when it reaches ASP.NET Core right? Can you do the reaction PR as well @maryamariyan ? |
ok, so as to update any usages in aspnetcore repo? |
Once the dependency PR comes in yea. |
Change API for the new
LoggerMessage.Define
overloads, to take LogDefineOptionsContributes to #50913