Skip to content

Fix type formatting in logging source generator test#124962

Open
svick wants to merge 1 commit intodotnet:mainfrom
svick:logging-test-failure
Open

Fix type formatting in logging source generator test#124962
svick wants to merge 1 commit intodotnet:mainfrom
svick:logging-test-failure

Conversation

@svick
Copy link
Member

@svick svick commented Feb 27, 2026

This happened because I didn't test #124638 and #124589 together (they contained changes that influenced each other).

This fixes the CI failure mentioned in #124957 (comment).

cc: @akoeplinger

Copilot AI review requested due to automatic review settings February 27, 2026 12:04
@svick svick enabled auto-merge (squash) February 27, 2026 12:04
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates a logging source generator baseline to match the generator’s current type-display formatting after prior related changes (generic method support + type formatting adjustments), ensuring the test suite reflects actual generated output.

Changes:

  • Adjusted the TestWithRefReadOnlyParam baseline to use C# keyword int instead of global::System.Int32 in generated signatures and LoggerMessage.Define<> calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants