Backport services, lineage, and data insight lazy-loading updates to 1.13

[shah-harshit]

Summary

• Backports OSS feat(ui): update Services & Ingestion components for lazy-load utility pattern #29066, feat(ui): update Entity & Lineage components for lazy-load utility pattern #29063, and feat(ui): update Dashboard, Pipeline, Chart & ML components for lazy-load utility pattern #29069 services, lineage, dashboard, pipeline, chart, ML, and data insight lazy-load utility updates on top of Group 14.
• Preserves the stacked review flow so this PR only shows Group 15 changes.

Stack

• Base branch: ui/backport-group14-explore-search-alerts-lazy-1.13
• Previous PR: Backport explore, search, and alerts lazy-loading updates to 1.13 #30135

Testing

• Scoped UI checkstyle sequence on changed source files: organize-imports-cli, ESLint --fix, Prettier.
• git diff --check ff94c4f..HEAD

[greptile-apps]

Too many files changed for review. (115 files found, 100 file limit)

Bypass the limit by tagging @greptile-apps to review.

[gitar-bot]

💡 Quality: Duplicate jest.mock for GenericContext in test

MlModelFeaturesList.test.tsx now has two jest.mock('../../Customization/GenericProvider/GenericContext', ...) calls (lines 145 and 154) targeting the exact same module path. Jest permits this and the last definition wins, so the earlier block is dead/redundant and misleading. Remove the stale first mock (or merge them) so the effective mock is obvious.

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 🚫 Blocked 0 resolved / 2 findings

Backports lazy-loading updates for services, lineage, and data insight components, but the build is currently blocked by an invalid import in PageViewsByEntitiesChart and duplicate mocks in MlModelFeaturesList.

🚨 Bug: CustomTooltip imported from module that doesn't export it

📄 openmetadata-ui/src/main/resources/ui/src/components/DataInsight/PageViewsByEntitiesChart.tsx:44-48

PageViewsByEntitiesChart.tsx now imports CustomTooltip from ../../utils/DataInsightPureUtils and renders it as <CustomTooltip />, but DataInsightPureUtils.ts does not export CustomTooltip — it is a JSX/React component that lives in DataInsightUtils.tsx (a .ts file cannot even hold JSX). This is a TS2305 "has no exported member" compile error and, if it slips past, would render an undefined component at runtime. Note DailyActiveUsersChart.tsx in the same PR correctly keeps CustomTooltip imported from DataInsightUtils. Split the import so only getGraphDataByEntityType/sortEntityByValue come from the Pure module and CustomTooltip stays from DataInsightUtils.

Keep CustomTooltip imported from DataInsightUtils (where it is actually exported), matching DailyActiveUsersChart.

import {
  getGraphDataByEntityType,
  sortEntityByValue,
} from '../../utils/DataInsightPureUtils';
import { CustomTooltip } from '../../utils/DataInsightUtils';

💡 Quality: Duplicate jest.mock for GenericContext in test

📄 openmetadata-ui/src/main/resources/ui/src/components/MlModel/MlModelDetail/MlModelFeaturesList.test.tsx:145 📄 openmetadata-ui/src/main/resources/ui/src/components/MlModel/MlModelDetail/MlModelFeaturesList.test.tsx:154-161

MlModelFeaturesList.test.tsx now has two jest.mock('../../Customization/GenericProvider/GenericContext', ...) calls (lines 145 and 154) targeting the exact same module path. Jest permits this and the last definition wins, so the earlier block is dead/redundant and misleading. Remove the stale first mock (or merge them) so the effective mock is obvious.

🤖 Prompt for agents

Code Review: Backports lazy-loading updates for services, lineage, and data insight components, but the build is currently blocked by an invalid import in PageViewsByEntitiesChart and duplicate mocks in MlModelFeaturesList.

1. 🚨 Bug: CustomTooltip imported from module that doesn't export it
   Files: openmetadata-ui/src/main/resources/ui/src/components/DataInsight/PageViewsByEntitiesChart.tsx:44-48

   PageViewsByEntitiesChart.tsx now imports `CustomTooltip` from `../../utils/DataInsightPureUtils` and renders it as `<CustomTooltip />`, but `DataInsightPureUtils.ts` does not export `CustomTooltip` — it is a JSX/React component that lives in `DataInsightUtils.tsx` (a `.ts` file cannot even hold JSX). This is a TS2305 "has no exported member" compile error and, if it slips past, would render an `undefined` component at runtime. Note DailyActiveUsersChart.tsx in the same PR correctly keeps `CustomTooltip` imported from `DataInsightUtils`. Split the import so only `getGraphDataByEntityType`/`sortEntityByValue` come from the Pure module and `CustomTooltip` stays from `DataInsightUtils`.

   Fix (Keep CustomTooltip imported from DataInsightUtils (where it is actually exported), matching DailyActiveUsersChart.):
   import {
     getGraphDataByEntityType,
     sortEntityByValue,
   } from '../../utils/DataInsightPureUtils';
   import { CustomTooltip } from '../../utils/DataInsightUtils';

2. 💡 Quality: Duplicate jest.mock for GenericContext in test
   Files: openmetadata-ui/src/main/resources/ui/src/components/MlModel/MlModelDetail/MlModelFeaturesList.test.tsx:145, openmetadata-ui/src/main/resources/ui/src/components/MlModel/MlModelDetail/MlModelFeaturesList.test.tsx:154-161

   MlModelFeaturesList.test.tsx now has two `jest.mock('../../Customization/GenericProvider/GenericContext', ...)` calls (lines 145 and 154) targeting the exact same module path. Jest permits this and the last definition wins, so the earlier block is dead/redundant and misleading. Remove the stale first mock (or merge them) so the effective mock is obvious.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[github-actions]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.