-
Notifications
You must be signed in to change notification settings - Fork 359
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
feat: add metadata column type badge #10052
Conversation
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10052 +/- ##
==========================================
- Coverage 54.35% 54.07% -0.28%
==========================================
Files 1259 448 -811
Lines 157337 77346 -79991
Branches 3644 3654 +10
==========================================
- Hits 85517 41827 -43690
+ Misses 71687 35385 -36302
- Partials 133 134 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
we wanna show types for all columns.
and keys need to be adjusted.
can we prioritize this PR over the PR about filter #10046? |
ef0ce65
to
2b673bb
Compare
2b673bb
to
22529d6
Compare
dff0977
to
d6ce663
Compare
c3b4786
to
6fde852
Compare
6fde852
to
d9d0f52
Compare
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.
Could you make sure this PR displays the columns' data correctly on #10066?
so far, it doesnt show data correctly.
@@ -63,6 +66,12 @@ interface ColumnTabProps { | |||
onHeatmapSelectionRemove?: (id: string) => void; | |||
} | |||
|
|||
export const formatColumnKey = (col: ProjectColumn): string => { |
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 think we wanna store all columns with types based on the discussion 2 weeks ago.
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.
this is basically used for mapping and encoding the UI part, which seems only necessary for the arbitrary metadata columns, as discussed with @ashtonG previously 😅
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.
just confirming -- as the only affected columns are run metadata columns, we should be okay to limit the type encoding to run metadata columns.
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.
As far as i know, hyperparameter would have the same names with different types too. i think its safer to encode all columns for the future and consistency.
1a7b2bf
to
1d1ddd1
Compare
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.
found a bug -- with multiple types of the same metadata column selected, changing the column width of one column changes the width of all columns with the same name. please make sure the column ids that we're sending to the datagrid component are correct.
78dda83
to
5ddcc36
Compare
8eba48a
to
f6c896e
Compare
KNOWN_BOOLEAN_COLUMNS.includes(col.column) && col.type === V1ColumnType.UNSPECIFIED | ||
? 'BOOLEAN' | ||
: removeColumnTypePrefix(col.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.
1009ae7
to
ccac19c
Compare
f4aa269
to
c801b0c
Compare
0a4e9c2
to
9ddcc0e
Compare
9ddcc0e
to
cbf0bb1
Compare
Closing PR due to company restructuring. |
Ticket
ET-791
Description
Right now, if we have multiple metadata columns with the same name, there's no quick way of knowing of which type each one is while selecting it. This PR intends to add a descriptive badge next to duplicate entries for the metadata columns.
Test Plan
<column_name> <column_type_tag>
formatChecklist
docs/release-notes/
See Release Note for details.