-
Notifications
You must be signed in to change notification settings - Fork 28
Removal of unverified Users from the leaderboard #67
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
base: version-1.2
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for computercodingtest ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Fix: Fixed Environment Variable Key for Noticeboard API Request
|
Same issue as PR-50, More than 1 API calls to codeforces server within 2 seconds is causing issues. |
Added License & Code of Conduct in the footer
CFdata contains some essential information related to present status of the CfId which will get updated as the user open its dashboard Leaderboard schema is to store the previous boards as it also allow developer to add feature to fetch the previous board and rating update can be done only as per the contest updates preprocessing total time: Codeforces Standing fetch + O(n*(time to save user data if participated) as codeforces standings is already in sorted order of its ranking also helps to get the ups and downs of the user compare to previous contest performance
/leaderboard <POST contestId> if a leaderboard already exist returns it if not fetch the previous board and creates new board with users in the previous board and also updatig the ranking if not participated but participated in the previous board then add them in the last with position update /updateCfdata to update the cf data as user opens the dashboard reducing the over head of multiple get req of fetching users data
i have resolve the issue u can test that as i am using api calls of the dashboard to update the content in avatar |
|
@adityarai0705 with it also solves the issue of EE1100 duplicate key error |
|
@smt96700 Please review it. |

@smt96700 this the new pull request i have created