-
Notifications
You must be signed in to change notification settings - Fork 650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support leetcode-cn #50
Comments
duplicate, sorry for annoying |
@Xeonacid I've received a lot of feedbacks about the Anyway, open an issue first is a good start I think. |
@jdneo I have found something below https://github.com/skygragon/leetcode-cli-plugins/blob/master/plugins/leetcode.cn.js I think these will be helpful... |
@Xeonacid Cool. Let me take a look. |
I have tried leetcode-cn plugin for leetcode-cli and it works fine. |
@zouyonghao Yes, I'm planning to add that plugin into the extension too. Will support leetcode.cn in next release. |
@Xeonacid @zouyonghao Can you submit solution to leetcode-cn using leetcode-cli? From my side I'm always getting |
@jdneo It seems there is a bug in leetcode.cn plugin, I have submit a pull request here |
@zouyonghao Cool. Let's have some discussion there. |
@zouyonghao Looks like the owner of leetcode-cli is busying with some stuff these ways. I'm deciding to embed your changes when building the extension and publish it this week. |
@jdneo That's cool, appreciate your working. |
LeetCode for VS Code 0.8.0 has been published in marketplace. Please have a try. |
@jdneo @zouyonghao Thanks! Good job! It works fine 👍 |
Haha, that could be a useful feature. Let’s tracking on that. |
LeetCode 中国 is the Chinese version of LeetCode. It provides a more comfortable experience for Chinese users, I think.
However, data of the universal version and the Chinese version of LeetCode is not shared. If we want, we have to sync them manually. So can we choose which version to use? 😃
Thanks!
BTW, I have learned that this extension is based on the leetcode-cli project. Maybe I had better open an issue there...
The text was updated successfully, but these errors were encountered: