-
Notifications
You must be signed in to change notification settings - Fork 28
Fix: Unverified user shown to the leaderboard also redesign the leaderboard with a point based positioning with sorted rating #50
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: main
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. |
|
I tried executing it several times on my local machine. Can't render the leaderboard. Could you please check?
|
|
The functionality is working fine, but I would greatly appreciate your input on enhancing the styling of the text displayed at the top. |
Is there any error occuring here as i am not getting such errors @smt96700 if u get such pls let me know |
i just saw the Tourist at the top so that is something it will solve and also there is one more error the site is rendering user profile based on cfid not verifying if it is verified or not which would create another pull request for it as there are serveral more such errors in registration as delete operation generally takes more time to process than create operation in mongodb database also one can add redis for otp verification instead of storing it in mongodb or in memory by creating a hash |
|
@Nishant040305 , Please create PR for branch 'version-1.2' and tag @smt96700 there for verification. @smt96700 , please verify it and get it merged asap. |
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





No description provided.