Skip to content
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

Makes runs table use hparam store for hparam columns #6736

Merged
merged 19 commits into from
Jan 31, 2024
Merged

Conversation

hoonji
Copy link
Member

@hoonji hoonji commented Jan 26, 2024

Motivation for features / changes

To display shared hparam columns across runs and scalar tables, both should read this data from the same hparam store. This PR first applies this change to the runs table.

Technical description of changes

Updates runs table to use columns from the hparam store, and to dispatch hparam actions

misc:

  • Loads hparams from local storage on persistentSettingsLoaded
  • Explicitly sets runs table header context menu options in selector (they will differ for scalar tables)
  • Shows "hidden" (i.e. disabled) columns in the runs table (hide will only apply to scalar tables)

Screenshots of UI changes (or N/A)

UI works the same

Detailed steps to verify changes work correctly (as executed by you)

Manually verified that adding/removing/filter columns is unchanged

WORKSPACE Outdated Show resolved Hide resolved
WORKSPACE Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why this change was needed. Can you please remove this file from this PR

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry buildifier keeps annoyingly swapping these lines. I'll add this change properly in a separate PR.

Comment on lines 334 to 336
let columns = [...runsTableHeaders, ...hparamColumns];
// Override hparam options to match runs table requirements.
columns = columns.map((column) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: It seems strange to initialize the column array, then immediately remap it.

Suggested change
let columns = [...runsTableHeaders, ...hparamColumns];
// Override hparam options to match runs table requirements.
columns = columns.map((column) => {
// Override hparam options to match runs table requirements.
const columns = [
...runsTableHeaders,
...hparamColumns,
].map((column) => {

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was also debating whether to combine these lines. I'll prefer conciseness going forward!

Base automatically changed from hparam_update_reorder to master January 31, 2024 12:58
@hoonji hoonji merged commit 78b36f8 into master Jan 31, 2024
16 checks passed
@hoonji hoonji deleted the hparam_runs_hparams branch January 31, 2024 14:09
@hoonji hoonji mentioned this pull request Jan 31, 2024
hoonji added a commit that referenced this pull request Feb 1, 2024
## Motivation for features / changes
Recently merged hparam column PRs (#6732, #6733, #6736) will cause build
and lint errors during 1p sync.

## Technical description of changes
- import map from rxjs/operators instead of rxjs
- `DataTableUtils` -> `dataTableUtils`
- use proper string signature on CardStateMap in tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants