rusackas opened a new pull request, #40912:
URL: https://github.com/apache/superset/pull/40912

   ### SUMMARY
   
   Adopts #37701 by @qf-jonathan — thank you for the substantial work here! 🙏
   
   Adds interactive **Sankey-based lineage** that lets users explore data 
relationships:
   
   - **Dataset lineage** — upstream database and downstream charts/dashboards
   - **Chart lineage** — database → dataset → chart → dashboards pipeline
   - **Dashboard lineage** — all upstream databases, datasets and charts 
feeding a dashboard
   
   **Implementation:** three REST endpoints 
(`/api/v1/lineage/{dataset|chart|dashboard}/<id>`) with permissions + 
integration tests, and a `LineageView`/`LineageModal` frontend (ECharts Sankey) 
surfaced from the dataset editor and the chart/dashboard action menus.
   
   ### What changed vs. the original PR
   
   Rebased onto current master and updated for drift accumulated since the 
original branch (Feb):
   - Resolved merge conflicts in `constants.py`, `ChartCard`, 
`useHeaderActionsDropdownMenu`, and the chart integration tests.
   - Repointed the lineage imports from the now-removed 
`@apache-superset/core/ui` to `@apache-superset/core/translation` and `/theme` 
(the package layout changed).
   - Re-applied the dataset lineage tab onto the **migrated (TypeScript)** 
`DatasourceEditor` (it was `.jsx` when the original PR was written).
   
   ### TESTING INSTRUCTIONS
   
   Open a dataset → **Lineage** tab; open a chart/dashboard menu → **Lineage**; 
verify the Sankey renders upstream/downstream relationships.
   
   Backend: `pytest 
tests/integration_tests/{charts,dashboards,datasets}/api_tests.py -k lineage`
   
   ### Verification status (honest notes for reviewers)
   
   - ✅ Backend static checks pass locally (mypy, ruff, pylint, license headers).
   - ✅ Frontend: prettier clean; the adopted TS files type-check cleanly after 
the import fixes.
   - ⚠️ `oxlint` and the backend **integration tests** weren't run in my 
environment (no DB); CI will exercise both.
   - ⚠️ End-to-end feature behavior is best confirmed with a manual smoke test 
in a running instance.
   
   ### ADDITIONAL INFORMATION
   
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [x] Changes UI
   - [ ] Includes DB Migration
   - [x] Introduces new feature or API
   - [ ] Removes existing feature or API
   
   Closes #37701
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to