-
Notifications
You must be signed in to change notification settings - Fork 773
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
Docs - logging best practice #5246
Docs - logging best practice #5246
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5246 +/- ##
==========================================
- Coverage 83.38% 83.12% -0.27%
==========================================
Files 297 271 -26
Lines 12531 11970 -561
==========================================
- Hits 10449 9950 -499
+ Misses 2082 2020 -62
Flags with carried forward coverage won't be shown. Click here to find out more.
|
* Starting from version `3.1.0`, the .NET runtime team is holding a high bar for | ||
backward compatibility on `Microsoft.Extensions.Logging` even during major | ||
version bumps, so compatibility is not a concern here. |
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.
I think "high bar" might not be clear to everyone. Maybe something like...
- Starting from version
3.1.0
the .NET runtime team has committed to preserve backwards compatibility on theMicrosoft.Extensions.Logging
packages. There will be no breaking changes (within reason) across major version bumps.
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.
I don't think we can put such strong statement #4920 (comment).
Add the initial doc for logging best practices.
Updated the logging benchmark to reflect the latest recommendations.