I added experimentListHidden to ExperimentPageUIState model. Then I changed ExperimentListView from class into functional React component in order to be able to use hooks and copied the method to load/save uiState from ExperimentView into ExperimentListView.

WIP because there's some problems. @daniellok-db can I get a hand with this? Do you approve of the approach? It seems like a lot of work for a relatively simple change, but I couldn't think of another way to do it.

1. The uiState is not being persisted correctly. For some reason, on page refresh the default value is being written to disk before it reaches ExperimentListView. I don't know why.
2. The component is being re-rendered more than it was. I don't know if this is a problem with the functional interface, but including those hooks causes several extra calls.
3. The Edit and Delete modals aren't being displayed. I haven't looked into it; I assume that's related to my change to a functional component.
4. I couldn't figure out what one part of the code was supposed to do. There's a part that calls list.forceUpdateGrid(), but the list ref doesn't seem to have that function when I change to functional useRef way of doing things.
5. I haven't run tests on it yet, since I don't know if this is the right way to go about it, and I know there's problems.

Related Issues/PRs

What changes are proposed in this pull request?

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

Interface

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

Language

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

Integrations

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)