Add DeepSeek and Qwen support with enhanced AI mistake analysis - #21
Open
xhuandy666 wants to merge 2 commits into
Open
Add DeepSeek and Qwen support with enhanced AI mistake analysis#21xhuandy666 wants to merge 2 commits into
xhuandy666 wants to merge 2 commits into
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
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.
Overview
This PR upgrades LeetCode EasyRepeat from v1.0.6 to v1.0.9 with first-class support for major Chinese LLM providers and a more reliable, useful AI-assisted mistake-analysis workflow.
Key changes
Chinese and multi-provider model support
/models, the UI falls back to recommended Qwen models.deepseek-r1integrations.Higher-quality mistake analysis
More reliable submission handling
Permissions and backend integration
Validation
main; this branch introduces no new full-suite failures.Testing note
No real paid-provider request was made because no personal API key was used. Provider requests, model discovery, prompt construction, capture states, and backend routing are covered by automated tests.