LeetCode(Modified)
❗️Attention❗️- This is a modified version that has merged some PR
- Change the configuration scope to window #698
Modified Repository
Solve LeetCode problems in VS Code
❗️ Attention ❗️- Workaround to login to LeetCode endpoint
Note: If you are using leetcode-cn.com , you can just ignore this section.
Recently we observed that the extension cannot login to leetcode.com endpoint anymore. The root cause of this issue is that leetcode.com changed its login mechanism and so far there is no ideal way to fix that issue.
Thanks for @yihong0618 provided a workaround which can somehow mitigate this. Now you can simply click the Sign In button and then select Third Party login or Cookie login.
Note: If you want to use third-party login(Recommended), please make sure your account has been connected to the third-party. If you want to use Cookie login, click here to see the steps.
Requirements
- VS Code 1.30.1+
- Node.js 10+
NOTE: Please make sure that Node is in your PATH environment variable. You can also use the setting leetcode.nodePath to specify the location of your Node.js executable.
Quick Start
Features
Sign In/Out
Switch Endpoint
By clicking the button at the explorer's navigation bar, you can switch between different endpoints.
The supported endpoints are:
- leetcode.com
- leetcode-cn.com
Note: The accounts of different endpoints are not shared. Please make sure you are using the right endpoint. The extension will use leetcode.com by default.
Pick a Problem
Directly click on the problem or right click the problem in the LeetCode Explorer and select Preview Problem to see the problem description.
Select Show Problem to directly open the file with the problem description.
Note:You can specify the path of the workspace folder to store the problem files by updating the setting leetcode.workspaceFolder . The default value is:$HOME/.leetcode/.
You can specify whether including the problem description in comments or not by updating the setting leetcode.showCommentDescription .
You can switch the default language by triggering the command: LeetCode: Switch Default Language .
Editor Shortcuts
Search problems by Keywords
- By clicking the button at the explorer's navigation bar, you can search the problems by keywords.
Manage Session
- To manage your LeetCode sessions, just clicking the
LeetCode: *** at the bottom of the status bar. You can switch between sessions or create, delete a session.
Settings
Setting Name |
Description |
Default Value |
leetcode.hideSolved |
Specify to hide the solved problems or not |
false |
leetcode.showLocked |
Specify to show the locked problems or not. Only Premium users could open the locked problems |
false |
leetcode.defaultLanguage |
Specify the default language used to solve the problem. Supported languages are: bash , c , cpp , csharp , golang , java , javascript , kotlin , mysql , php , python ,python3 ,ruby ,rust , scala , swift , typescript |
N/A |
leetcode.useWsl |
Specify whether to use WSL or not |
false |
leetcode.endpoint |
Specify the active endpoint. Supported endpoints are: leetcode , leetcode-cn |
leetcode |
leetcode.workspaceFolder |
Specify the path of the workspace folder to store the problem files. |
"" |
leetcode.filePath |
Specify the relative path under the workspace and the file name to save the problem files. More details can be found here. |
|
leetcode.enableStatusBar |
Specify whether the LeetCode status bar will be shown or not. |
true |
leetcode.editor.shortcuts |
Specify the customized shortcuts in editors. Supported values are: submit , test , star , solution and description . |
["submit, test"] |
leetcode.enableSideMode |
Specify whether preview , solution and submission tab should be grouped into the second editor column when solving a problem. |
true |
leetcode.nodePath |
Specify the Node.js executable path. for example, C:\Program Files\nodejs\node.exe |
node |
leetcode.showCommentDescription |
Specify whether to include the problem description in the comments |
false |
leetcode.useEndpointTranslation |
Use endpoint's translation (if available) |
true |
Want Help?
When you meet any problem, you can check out the Troubleshooting and FAQ first.
If your problem still cannot be addressed, feel free to reach us in the Gitter Channel or file an issue.
Release Notes
Refer to CHANGELOG
Acknowledgement
| |