zerotrac / zerotrac/leetcode_problem_rating
Take a look at this issue if you come up with more features
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 693
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
The aim of this whole project is to:
- Calculate the rating of every contest problem based on the statistics of the corresponding participants. This part is not open-sourced.
- Store the ratings in a file called
ratings.txtin this repository. - Visualize the ratings in a user-friendly way by developing a frontend. This part is open-sourced and is also in this repository.
If you would like to use the data to customize your own LeetCod-ing plan (e.g. solving problems that have rating ~200 more than your current rating), you can just use the ratings.txt file. It is well-structured, taking <10 minutes programming in Python to parse everything. I may not try to develop features like #12 (add tags for each problem) or #14, because a LeetCode-like website is not what I am aiming at.
The best way to use this project is:
- If you need a quick check of the problem rating, just use the website. You can choose a specific problem or contest, search by keyword, sort, and filter by a rating interval.
- If you would like to have a customized LeetCod-ing plan, you can use the
ratings.txtfile to track your own pace.
I am pretty sure that the LeetCode official are now working on similar features. After the official version is fully developed, it will be something showing together with the problems in the LeetCode website, so all the issues will no longer exist anymore.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No concrete feature, file, or test is specified. Read the frontend and ratings.txt context to identify a bounded proposal; what counts as done cannot be defined until a specific feature and acceptance criteria are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100