UI: match count to bottom, remove overview CTAs, calmer upload status - #144
Merged
Conversation
- Move the '<N> cases match' filter count out of the library header into a fixed bar at the bottom-left of the screen, so it's out of the way while filtering. - Remove the Browse Dataset / Upload Dataset buttons from the landing/overview hero (and the now-unused navigate). - Replace the per-scan spinning wheel with a subtle pulsing status dot, so multiple in-flight uploads don't each spin; the single spinner stays in the batch summary bar.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses several UI asks. Three landed here; two more (CT-count accuracy, shuffle speed) are noted below and I'll follow up.
In this PR
navigate).Typecheck passes (
tsc -b, verified on the server toolchain).Follow-ups (need a decision / investigation)
TARGETS.ctVolumesinLandingPage. I didn't want to guess a new wrong number on a public page — what's the correct count, or should I make it dynamic (fetch the real dataset total)?