Logging Analyzer: Add code fixer for CA1727 and CA1848

[maryamariyan]

We shipped logging analyzer diagnostics in 6.0, approved in issue dotnet/runtime#36064.

This issue tracks adding fixer for two of them:

• CA1727: easy fixer, would involve uppercasing the named placeholder so it becomes pascal case.

• CA1848: this diagnostic encourages using LoggerMessage delegates. The fixer could involve making use of the logging source generator as a code suggestion.

[ghost]

Tagging subscribers to this area: @maryamariyan
See info in area-owners.md if you want to be subscribed.

Issue Details

---

We shipped logging analyzer diagnostics in 6.0, approved in issue dotnet/runtime#36064.

This issue tracks adding fixer for two of them:

• CA1727: easy fixer, would involve uppercasing the named placeholder so it becomes pascal case.

• CA1848: this diagnostic encourages using LoggerMessage delegates. The fixer could involve making use of the logging source generator as a code suggestion.

Author:	maryamariyan
Assignees:	-
Labels:	area-Extensions-Logging, code-analyzer
Milestone:	7.0.0

[flcdrg]

FYI the documentation is missing for CA1848. The link from the analyzer - https://docs.microsoft.com/en-au/dotnet/fundamentals/code-analysis/quality-rules/ca1848 results in a 404

[maryamariyan]

FYI the documentation is missing for CA1848. The link from the analyzer - https://docs.microsoft.com/en-au/dotnet/fundamentals/code-analysis/quality-rules/ca1848 results in a 404

This issue is tracked by dotnet/docs#23900

[carlossanlop]

@maryamariyan do you plan on addressing these bug fixes in 7.0?

[buyaa-n]

@maryamariyan looks the fixers proposed here are approved with the original API proposal, is that right? If so, we don't need to keep this issue in runtime, better to be transferred to the analyzer's repo for further implementation