Skip to content

feat(types): widen 291 nullable response fields to Optional - #74

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 field the public spec marks nullable but the SDK typed as a bare value is now Optional[...]. Requiredness and shapes untouched. The audit's nullability finding count drops from 291 to 0. Full gauntlet green locally (pytest 243, pyright, mypy, ruff, sync --check).

https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs

The spec marks these fields nullable but the SDK typed them as bare
values, so type checkers rejected valid None handling in consumer code.
Mechanical widening only: no requiredness or shape changes. Audit
nullability count goes 291 to 0.

Claude-Session: https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs
@ericviana
ericviana merged commit 2810f7f into main Aug 4, 2026
@ericviana
ericviana deleted the eric/nullability-widening branch August 4, 2026 19:54
@BernardoSM

Copy link
Copy Markdown
Collaborator

✅ 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