-
Notifications
You must be signed in to change notification settings - Fork 2.7k
feat: LEAP-2036: Summary page for View All #7439
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: develop
Are you sure you want to change the base?
Conversation
Create a special Summary page inside View All view to display all labelings across all annotations in current task. Here are the LabelingSummary and DataSummary components to display info about control tags and object tags respectively.
Proper user info for Userpic and `user` in store. Proper types for them.
✅ Deploy Preview for label-studio-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for heartex-docs canceled.
|
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
@@ -47,7 +47,8 @@ import { ToastProvider, ToastViewport } from "@humansignal/ui/lib/toast/toast"; | |||
import { Annotation } from "./Annotation"; | |||
import { BottomBar } from "../BottomBar/BottomBar"; | |||
import Debug from "../Debug"; | |||
import Grid from "./Grid"; | |||
// import Grid from "./Grid"; | |||
import Summary from "../Summary/Summary"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would use a more precise name for this component given it is pretty open, maybe AnnotationSummary
or ReviewSummary
or anything else that gives a bit more information
<table className="table-auto w-full"> | ||
<thead> | ||
<tr> | ||
{Object.entries(data_types).map(([field, type]) => ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a check here so we can safely assume we will have data_types
|
||
export const LabelingSummary = ({ annotations, controls }: Props) => { | ||
return ( | ||
<table className="w-full"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless specifically needed I would use Grid over tables so we can easily ensure a responsive design
It chooses between tabbed view with FF ON and usual Grid with FF OFF. Tabbed view has new Summary tab and old Grid tab. Selected tab is preserved between sessions.
- no tooltip on avatar, we already show names - annotation tabs are always displayed with new Summary
- Add TextArea tag - Add support for per-regions - for now per-region flag is calculated by simple rule: >1 results -> per-region - Move renderers to a separate file - Allow to return null to fallback to default text
More semantic styles. Local Card component. Numbers on the top.
All labels will be displayed the same, so just reuse the same renderer.
Agreement is calculated on backend over submitted annotations. So displayed results should also be only submitted once. We have `versions` with `draft` and `result`, so we should use the latter.
Get (almost) all info about tags from LSF; don't use DM. The only lefover is agreement, should be fixed soon. Fix all the related code to work with real tags. Add new types to describe store and tags. Fix linting here and there.
This automatically accepts agreement passed via `task` from outer sources.
/git merge
|
…tudio into fb-leap-2036/summary
Create a special Summary page inside View All view to display all labelings across all annotations in current task.
Here are the
LabelingSummary
andDataSummary
components to display info about control tags and object tags respectively.