Merge to main #245
Merge to main #245
Conversation
…learskyUI into rework-block-stats-table-view
Reworked blocked stats table. I divided the different datasets into their own tables, which can be accessed by clicking the tabs. However, the addition of the four tables is a slight deviation from the original request in the issue, so let me know if you still want the last blocked datasets combined instead. https://github.com/user-attachments/assets/90b2961c-2ab4-477c-b755-c52e769c408a
I updated the conditional rendering to fix the list count header bug. The first search is what's currently deployed, and the second search is the fix on my local. https://github.com/user-attachments/assets/0d3a6e10-de52-4432-885a-6ceafc43ef40
Signed-off-by: Justin <[email protected]>
Signed-off-by: Justin <[email protected]>
add Clearsky status page link to top row hyperlinks
Updated code to handle new top lists data format. https://github.com/user-attachments/assets/6fa17f3b-9622-4871-9e6c-923c9843408d
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
passed functionality checks. |
|
top 24 profiles not resolving correctly. There seems to be some wonky things going on with how the profiles are loading. I'm not sure if its a rate limit issue or a logic issue.
|
|
from what i can tell it's neither. all those accounts are banned already and don't resolve as actors from the bsky api (see the same behavior in prod as well) |
|
Ah, it must have happened between refreshes. Do we want to not show the account if it can't resolve? I've put measures in place in the backend to not return inactive accounts but there is a 12 hour gap between refreshes. |
|
Pending #256 |
|
when using /?api=prod and navigating to the labels tab I get this error:
|
|
Labels did load after the reload |
this will also fix the crash we're seeing when our current dev branch queries against the prod api without a return added for the all the labelers
|
Looks like labels tab is broken. |
Lints readme, updates packages to resolve a high vuln, and flips copyright notice from 2024 to 2025.
- Updates readme based on linter - This isn't necessary, but I like to use a very particular markdown linter (it hates spaces at the end of a line, amongst other things). - Updates packages to resolve a high vuln - Ran `npm update` for 2 specific packages, not on the entire package library. Hence the smaller package-lock update. - `npm audit` will now show 0 vulns (constant vigilance is needed, of course) - Copyright tag change from 2024 to 2025 - We in the future now woot woot!
Pending #244 investigation