As of right now, the current leaderboard and leaderboard with ID has a lot of duplication, which causes accidental UI drift. Schedule a meeting with @Tahmid Ahmed to discuss in more detail about how this needs to get done since this is a heavy task
-
also and combine LeaderboardMetadata (this is everything up the top three tier)
-
handle query with and without ID (use leaderboardId? maybe)
-
need to have a way to track if ID is available or not
-
need a way (can be a prop) to differ them slightly (for example, leaderboard with ID has a tooltip over each user entry saying that profiles cannot be viewed at that time)

-
UI (the component) needs to be shared (same one UI)
It doesn’t matter so much how you do it, some options are better than others so take your time and think about it, but the main goal is that the UI doesn’t need to be copy pasted between each type.
isPrevious
AC:
- Compare
stg to prod
- Current leaderboard should be functionally the same
- Leaderboard name + syntax highlighting
- Users
- padding
- filters
- pagination
- search
- Leaderboard with ID always lags behind by accident, so if there’s disreprancies it should match current leaderboard
Resolution:
- hoist the query to be outside of these components