[UI] Improve empty states across Experiments, Models, Prompts, and Gateway pages#20044
Conversation
…teway pages - Updated empty states to use Databricks design system Empty component with proper icons - Added plus icons to all 'Create' buttons for consistency - Made empty states centered with proper styling - Ensured table headers and search bars remain visible in empty states - Updated empty state descriptions with helpful text and documentation links - Removed padding inconsistencies across Models page - Removed AI Gateway icon from header - Hide action buttons in headers when empty state is shown Signed-off-by: ridgupta26 <ridhima.gatech@gmail.com>
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
|
@ridgupta26 Thank you for the contribution! Could you fix the following issue(s)? ⚠ DCO checkThe DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details. ⚠ Invalid PR templateThis PR does not appear to have been filed using the MLflow PR template. Please copy the PR template from here and fill it out. |
Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
| onDelete={() => handleDeleteClick(endpoint)} | ||
| /> | ||
| ))} | ||
| {showEmptyState ? ( |
There was a problem hiding this comment.
@ridgupta26 It seems the div is not centered properly
There was a problem hiding this comment.
hmm i also think it's weird to put the empty state inside a row. i'm going to revert to using the empty prop as before unless there's a specific reason for this
|
Documentation preview for 39bcd62 is available at: More info
|
- Fixed vertical centering of empty state in EndpointsList by applying height and vertical-align to td element - Applied prettier formatting to ExperimentListTable, ExperimentListView, and ExperimentsHomeView - Empty state now properly centered with consistent styling Signed-off-by: ridgupta26 <ridhima.gatech@gmail.com>
|
@B-Step62 Fixed the Gateway empty state centering issue. The empty state is now properly vertically centered by applying |
a5f06bf to
0e16f41
Compare
|
Fixed DCO issue - the sign-off email now matches the author email for all commits. All checks are now passing! ✅ |
mlflow/server/js/src/experiment-tracking/pages/prompts/components/PromptsListTable.tsx
Outdated
Show resolved
Hide resolved
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
…teway pages (mlflow#20044) Signed-off-by: ridgupta26 <ridhima.gatech@gmail.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Signed-off-by: Daniel Lok <daniel.lok@databricks.com> Co-authored-by: ridgupta26 <ridhima.gatech@gmail.com> Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: Daniel Lok <daniel.lok@databricks.com>
…teway pages (#20044) Signed-off-by: ridgupta26 <ridhima.gatech@gmail.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Signed-off-by: Daniel Lok <daniel.lok@databricks.com> Co-authored-by: ridgupta26 <ridhima.gatech@gmail.com> Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: Daniel Lok <daniel.lok@databricks.com>
Before





After
CleanShot.2026-01-15.at.15.03.26.mp4
Related Issues/PRs
What changes are proposed in this pull request?
This PR improves the empty states across multiple pages in the MLflow UI to provide a more consistent and user-friendly experience:
Changes:
Emptycomponent with appropriate iconsPages affected:
How is this PR tested?
Manual testing performed:
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Improved empty state UI across Experiments, Models, Prompts, and Gateway pages with consistent styling, better icons, and helpful action buttons. Table headers and search bars now remain visible in empty states for better user orientation.
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?