Skip to content

feat(types): widen 99 nullable response fields (v3.4.0) - #43

Merged
ericviana merged 1 commit into
mainfrom
eric/nullability-widening
Aug 4, 2026
Merged

ericviana merged 1 commit into
mainfrom
eric/nullability-widening

Conversation

@ericviana

Copy link
Copy Markdown
Member

Mechanical nullability catch-up: every response field the public spec marks nullable but the SDK typed non-nullable is now ?T with null-safe decoding, following the codebase's existing nullable idioms. The audit's nullabilityMismatch count drops from 99 to 0. Pest, lint, contract-check and sync --check green locally.

https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs

The spec marks these fields nullable but the SDK typed them as
non-nullable, so decoding a null crashed or type checks rejected valid
handling. Mechanical widening following the codebase's existing
nullable idioms; audit nullability count goes 99 to 0.

Claude-Session: https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs
@ericviana
ericviana merged commit 769f5cc into main Aug 4, 2026
3 of 4 checks passed
@ericviana
ericviana deleted the eric/nullability-widening branch August 4, 2026 19:55
@BernardoSM

Copy link
Copy Markdown
Contributor

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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