https://github.com/ravsii/better-leetcode

Solve Leetcode problems in VSCode
https://github.com/ravsii/better-leetcode

leetcode vscode vscode-extension

Last synced: 10 days ago
JSON representation

Solve Leetcode problems in VSCode

• Host: GitHub
• URL: https://github.com/ravsii/better-leetcode
• Owner: ravsii
• License: bsd-3-clause
• Created: 2024-03-12T18:06:09.000Z (10 months ago)
• Default Branch: main
• Last Pushed: 2024-03-27T21:01:42.000Z (10 months ago)
• Last Synced: 2024-11-08T08:27:11.698Z (2 months ago)
• Topics: leetcode, vscode, vscode-extension
• Language: TypeScript
• Homepage:
• Size: 131 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Better Leetcode

Solve leetcode problems inside VSCode.

Note: This is still in alpha:

* ⚠️ Works only for EU endpoint (for now)

* ⚠️ Only cookie auth is supported at the moment

## Compatibility

We decided not to reinvent the wheel and adopt the same format as [vscode-leetcode](https://github.com/LeetCode-OpenSource/vscode-leetcode) has for file parsing.

`// @lc code=start` and `// @lc code=end` are used to denote the beginning and the end of the solution.

You can keep using your old files with this extension, yay! (It works the other way around, too!)

## Motivation

This was born mainly due to [vscode-leetcode](https://github.com/LeetCode-OpenSource/vscode-leetcode) being abbandoned and having multiple issues:

* Using extra CLIs under the hood instead of queries LeetCode API directly

* Missing features, like custom tests adding custom tests

* Having no information about what the current daily question is

* Missing visualization for trees and other DS (although this one is very minor, but if we can implement that - then why not)

## Progress

* [x] Auth (Session handler)

* [x] Request API

* [x] Problem list

* [x] Preview Problem

* [x] Open problem as code

  * [x] `// @leet` tags as begin/end tags

* [ ] Sending submissions

  * [ ] Tests

    * [ ] Add \ Delete \ Edit tests within vscode (vscode-leetcode can't do that)

  * [ ] Submissions

  * [ ] Result screen

* [x] Daily question

* [ ] Stats - In Progress

* [ ] Search

* [ ] Sessions

* [x] Settings

  * [x] Langs (2 setting options for preferred / fallback languages)

  * [x] Files location

## Inspiration

* [vscode-leetcode](https://github.com/LeetCode-OpenSource/vscode-leetcode) as a battle-tested extension example.

* [leetcode.nvim](https://github.com/kawre/leetcode.nvim) as an example of how a proper extension (plugin) should look and behave like.