fix(ai): narrow external data to unknown and add guards#195
Open
awwalmust wants to merge 6 commits into
Open
Conversation
…der; adjust eslint overrides
Collaborator
|
Resolve conflict please @awwalmust |
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
2 participants
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.
Replace unsafe 'any' with 'unknown' in AI interfaces and providers, add lightweight normalization/guards in OpenAIProvider, and adjust ESLint overrides so src/** files are linted without type-aware rules. This reduces runtime risk from untrusted AI data and clears lint warnings. Local checks: npm run format && npm run lint (no explicit-any warnings for AI files).