Enhance TypeScript strictness with explicit types and runtime validation #118
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.
Replaced loose typing (
Record<string, unknown>) with explicit types and added runtime validation for LLM API responses. Enabled additional strict compiler options.Type System Improvements
PartialGameDataandGeneratedGameDatatypes derived fromGameinterfaceas unknown asassertions with properWindowWithEnvandImportMetaEnvinterfacesPartialGameDatainstead of generic recordsRuntime Validation
Added
isValidGameData()type guard validating API response structure:Responses are validated before type casting, preventing runtime type mismatches.
Compiler Options
Added to both
tsconfig.app.jsonandtsconfig.node.json:noUncheckedIndexedAccess- prevents unsafe array/object accessnoImplicitOverride- requires explicit override keywordsnoPropertyAccessFromIndexSignature- enforces bracket notation for index signaturesZero
anytypes remain in codebase.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.