Skip to content

Update nullable review rule to check project-level setting#11073

Open
jonathanpeppers wants to merge 2 commits intomainfrom
dev/peppers/fix-nullable-review-rule
Open

Update nullable review rule to check project-level setting#11073
jonathanpeppers wants to merge 2 commits intomainfrom
dev/peppers/fix-nullable-review-rule

Conversation

@jonathanpeppers
Copy link
Copy Markdown
Member

Skip flagging missing per-file #nullable enable when the project's .csproj already has <Nullable>enable</Nullable>.

Found during PR #10862 review — src/Microsoft.Android.Run/AdbHelper.cs was flagged for missing #nullable enable but the project already enables it at the project level.

Skip flagging missing per-file #nullable enable when the project's .csproj
already has <Nullable>enable</Nullable>.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
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 the repository’s AI/code review checklist to avoid incorrectly flagging missing per-file #nullable enable directives when nullable reference types are already enabled at the project level.

Changes:

  • Adjusts the “#nullable enable” rule to exempt projects that already set <Nullable>enable</Nullable> in their project file.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants