fix(types): validate unsafe cast boundaries - #1661
Open
open-inspect[bot] wants to merge 1 commit into
Open
Conversation
Terraform Validation Results
Pushed by: @open-inspect[bot], Action: |
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
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.
This is an automated nightly unsafe-cast remediation sweep. It addresses three currently qualifying unsafe TypeScript cast findings by parsing or guarding at the boundary, following the TypeScript Coding Standards for unsafe casts / parse-don't-assert and the Zod boundary-validation pattern established in PR #807.
packages/shared/src/completion/extractor.ts:332/:358/:363/:411args/metadatavalues were treated as records after assertionpackages/web/src/app/api/sessions/[id]/sandbox-access/route.ts:21409JSON body was asserted as{ error?: unknown }packages/control-plane/src/session/ws-client-mapping-repository.ts:48WsClientMappingResult[]WsClientMappingResultaz.infertype; nullable D1 profile fields are modeled as nullableVerification:
npm run build -w @open-inspect/sharednpm run build -w @open-inspect/control-planeNODE_ENV=production npm run build -w @open-inspect/webnpm run typechecknpm run lintnpm run formatnpm test -w @open-inspect/sharednpm test -w @open-inspect/control-planenpm test -w @open-inspect/webNote:
npm run build -w @open-inspect/webfailed once under the shell's non-standardNODE_ENVwith a Next/_global-errorprerenderuseContexterror, then passed withNODE_ENV=production. Two web ESLint-boundary tests also timed out when the full web suite ran concurrently with repo-wide checks, then the isolated final web test run passed.References: TypeScript Coding Standards unsafe-cast / parse-don't-assert guidance, and the Zod boundary-validation pattern established in PR #807.
Created with Open-Inspect