This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
66 use datatable in live submissions #70
Merged
Clumsy-Coder
merged 22 commits into
development
from
66-use-datatable-in-live-submissions
Jan 3, 2024
Merged
66 use datatable in live submissions #70
Clumsy-Coder
merged 22 commits into
development
from
66-use-datatable-in-live-submissions
Jan 3, 2024
Conversation
This file contains 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
## what - add component `Badge` ## how - run command npx shadcn-ui@latest add badge ## why - this component will be used to display the verdict in `LiveSubmissions` ## where - ./src/components/ui/badge.tsx ## usage
## what - add `columns.tsx` for home page - display the `Submission ID` column ## how ## why - this will be used to display live submissions on the home page ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - display the `DataTable` for live submissions ## how ## why - using the `DataTable` will allow - filter the table - sort columns - show/hide columns - use pagination - reusing code to keep the code base lean ## where - ./src/app/page.tsx ## usage
## what - use `DataTable` loading component ## how ## why - reusing code - easy way to display skeleton data table with varying columns and rows ## where - ./src/app/page.tsx ## usage
…ions data-table ## what - display `problem number` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ons data-table ## what - display `problem title` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ata-table ## what - display `username` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ta-table ## what - display `verdict` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ata-table ## what - display `language` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ta-table ## what - display `runtime` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…table ## what - display `rank` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…s data-table ## what - display `submit time` in live submissions data-table ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
…ble` ## what - add styling to live submissions `DataTable` - show underline for `submission id` cells - show underline for `problem number` cells - show underline for `problem title` cells - show underline for `username` cells - align right `submit time` column - remove css classes for `buttonVariant` ## how ## why - to make it look better - to make the table fit in a laptop sized screen without overflowing ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - disable column sorting in live submissions ## how ## why - they have no purpose in sorting - they take up space, causing the table to overflow in x-axis ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - set string names in the column dropdown ## how ## why - before the dropdown would use the column `accessorKey` as a string to display - now it's manually set to have a better look ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - add component `Tooltip` ## how - run command npx shadcn-ui@latest add tooltip ## why - will be used when hovering over `submit time` cell in live submissions ## where - ./package-lock.json - ./package.json - ./src/components/ui/tooltip.tsx ## usage
## what - display submit time using tooltip ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - add fgColor for `verdict` ## how ## why ## where - ./src/types/index.ts ## usage
## what - format code ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
… DataTable ## what - add padding to links in live-submission DataTable ## how ## why ## where - ./src/app/components/data-table/columns.tsx ## usage
## what - add page title ## how ## why ## where - ./src/app/page.tsx ## usage
## what - update images for home page - loading - data loaded ## how ## why ## where - ./docs/images/page-home-loading.png - ./docs/images/page-home.png ## usage
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🎉 This PR is included in version 1.0.0-development.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Make Live submissions table searchable
Description
badge
to display VerdictfgColor
fgColor
toVerdict
typeRelated Issue
#66
Motivation and Context
To make the table searchable.
How Has This Been Tested?
Screenshots (if appropriate)
Types of changes
Does this Pull Request introduce a breaking change?
Checklist