-
Notifications
You must be signed in to change notification settings - Fork 356
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: support filter in flat run table #9250
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 #9250 +/- ##
==========================================
- Coverage 44.60% 37.91% -6.69%
==========================================
Files 1275 951 -324
Lines 156240 116539 -39701
Branches 2450 2450
==========================================
- Hits 69687 44183 -25504
+ Misses 86313 72116 -14197
Partials 240 240
Flags with carried forward coverage won't be shown. Click here to find out more.
|
85c772c
to
a60df55
Compare
0678ca5
to
4be7477
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.
-
noticed that Searcher Metrics Value does not show filter options in header menu but it does still appear in the Filters dropdown menu. This is true for Experiments List, too. But maybe worth addressing here?
-
Also, it looks like the Searcher ID and Searcher Description columns appear in the table but can't be filtered, even though they're not in
BANNED_FILTER_COLUMNS
(and I don't think we would want them to be?). I think we just need to make sure everything ingetColumnDefs
andrunColumns
matches. May need to update again with feat: Add Run columns to GetProjectColumns #9146 but should probably make sure current columns work with filters as expected. -
Also not sure why, but I don't think ID filter is working. Returns no results even when I'm expecting one to be returned.
4be7477
to
0630fad
Compare
fixed in run table and experiment table
Searcher ID filter exits as ID . Search Name filter exits as Name . Searcher Description filter exits as Description .imo these names shouldn't be overwritten in frontend. that causes the name mismatching like this. @johnkim-det what do you think is the best solution for this? If we wanna keep the current column names, we need to fix backend. if we wanna change the column name, these should match the column data from backend. i think backend change is required for either way
|
yeah I think it makes sense to always use the names from the backend -- might be better to read the names from But I'm less concerned with the mismatch of column names between filters menu and column headers than the fact that the column header menus aren't displaying filter options at all for those columns. the name mismatch shouldn't cause that, right? |
Right, the name mismatch doesnt cause the issue. Backend doesnt return these columns. thats the issue. i dont think web cant do anything with this until backend return missing 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.
OK I see now that the filter options are based on projectColumns
while displaying the column is based on settings.columns
/FE definition. Not sure if it's good to have two different places where columns are defined like that, but I guess it's out of scope of this PR either way.
It does look like #9146 will provide experimentId
and experimentDescription
in projectColumns
. might be a good idea to try those changes with yours to make sure that at least everything filter-related will work.
but will approve this assuming those two columns are the only issues, since they'd be addressed with #9146 merge.
ID filter not working is a different problem, do you mind making a ticket for that so it's captured for grooming discussion?
made a ticket |
Ticket
ET-111
Description
Add filter feature in Flat Run table (Run table is under feature flag)
Test Plan
(filter behavior should be the same as the experiment table we have now (its not feature flagged))
Checklist
docs/release-notes/
.See Release Note for details.