Skip to content

Drop redundant null-response guard from Sample.Cli (6.0.0 follow-up)#20

Merged
marklauter merged 1 commit into
mainfrom
lauterm/sample-cli-null-guard
Jun 30, 2026
Merged

Drop redundant null-response guard from Sample.Cli (6.0.0 follow-up)#20
marklauter merged 1 commit into
mainfrom
lauterm/sample-cli-null-guard

Conversation

@marklauter

Copy link
Copy Markdown
Owner

Follow-up to #19 (the 6.0.0 non-nullable Response/InvokeAsync change).

InvokeAsync now returns a non-nullable response, so the if (report is null) return 1 guard in Sample.Cli/Program.cs is dead code. Removed it; the error path keeps exit code 2.

The wiki Sample-CLI walkthrough and exit-code table are updated to match (separate wiki commit).

Verification

  • dotnet build / dotnet format --severity info --verify-no-changes — clean
  • dotnet test — 179 passed, 0 failed

🤖 Generated with Claude Code

InvokeAsync returns a non-nullable response in 6.0.0, so the
`if (report is null) return 1` guard is dead. Remove it; the error path
keeps exit code 2. Walkthrough wiki page updated to match.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@marklauter marklauter merged commit 2d0ea02 into main Jun 30, 2026
8 checks passed
@marklauter marklauter deleted the lauterm/sample-cli-null-guard branch June 30, 2026 21:22
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.

1 participant