Skip to content

Reader: async ReadOrNullAsync with a nullable result (4.4.0) - #225

Merged
ognjenkatic merged 1 commit into
masterfrom
failed-task-reader-read-or-null
Aug 27, 2026
Merged

Reader: async ReadOrNullAsync with a nullable result (4.4.0)#225
ognjenkatic merged 1 commit into
masterfrom
failed-task-reader-read-or-null

Conversation

@ognjenkatic

Copy link
Copy Markdown
Collaborator

Renames FailedTaskStructuredErrorReader.TryRead (bool + out, synchronous) back to an async method: Task<StructuredError?> ReadOrNullAsync(...). The Try shape forced the method synchronous — async methods cannot have out parameters — and blocking on the Conductor call is worse than the null-returning read. The file opts into #nullable enable so the contract is explicit: ReadOrNullAsync and FindDeepestFailedTaskAsync may return null, ReadOrFallbackAsync never does.

4.4.0 is not on nuget.org yet, so no version bump.

🤖 Generated with Claude Code

…result
Restores the async signature; the Try shape forced the method
synchronous since async methods cannot have out parameters.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ognjenkatic
ognjenkatic merged commit fa9e5c9 into masterAug 27, 2026
1 check passed
@ognjenkatic
ognjenkatic deleted the failed-task-reader-read-or-null branch August 27, 2026 09:11
Sign up for freeto 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

@ognjenkatic