test(sdk): type-check live request payloads#479
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update both SDK live suites to use the current
textrequest field instead of removedbody, and make stale request shapes fail during normal test runs. TypeScript now type-checks source plus tests; Python runs mypy against its typed live suite in CI.Client surface checklist
texttextNo server, OpenAPI, CLI, or MCP behavior changes are included.
Operational risk
Test and CI-only changes. The stricter gates may expose future stale examples before runtime; they do not change published SDK runtime behavior.
Test plan
npm run build --workspace @e2a/sdknpm test --workspace @e2a/sdk— 155 passednpm run test:live --workspace @e2a/sdk— collected, 4 skipped without live credentialsmypy— no issuespytest tests/ -q— 277 passed, 18 skippedNote:
uv lock --checkpanicked in the local macOS system-configuration library; the committed lock installed successfully and powered the passing Python suite.