feat(sdk) add dashboard & chart entity

[yoonhyejin]

Adds Dashboard & Charts entity to SDK.

Supported actions

• add input datasets to chart ( == upstream dataset)
• add input datasets to dashboard ( == upstream dataset)
• add chart to dashboard ( "contents" of a dashboard)
• add dashboards to dashboard ( == upstream dashboard)

[codecov]

Codecov Report

Attention: Patch coverage is 84.53608% with 60 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
metadata-ingestion/src/datahub/sdk/dashboard.py	78.44%	47 Missing ⚠️
metadata-ingestion/src/datahub/sdk/chart.py	91.66%	13 Missing ⚠️

📢 Thoughts on this report? Let us know!

[alwaysmeticulous]

🔴 Meticulous spotted visual differences in 4 of 1347 screens tested: view and approve differences detected.

Meticulous evaluated ~10 hours of user flows against your PR.

_{Last updated for commit 2a309f9. This comment will update as new commits are pushed.}

[codecov]

Bundle Report

Changes will decrease total bundle size by 3.76kB (-0.02%) ⬇️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
datahub-react-web-esm	19.65MB	-3.76kB (-0.02%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: datahub-react-web-esm

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
assets/index-*.js	-3.76kB	16.02MB	-0.02%

[Copilot]

Pull Request Overview

This PR adds new Dashboard and Chart entities to the SDK along with their respective tests, golden files, and example usage. Key changes include:

• New tests and golden files for Dashboard and Chart entities
• Updates to the entity client, SDK internals, and examples for handling Dashboard and Chart operations
• Adjusted type aliases and entity registry to support new entities

Reviewed Changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tests/unit/sdk_v2/test_dashboard.py	Adds basic and complex tests for Dashboard entity functionality.
tests/unit/sdk_v2/test_chart.py	Adds tests for Chart entity functionality including input dataset operations.
dashboard_golden and chart_golden JSON files	Provide expected golden outputs for Dashboard and Chart entities.
src/datahub/sdk/entity_client.py	Adds overloads for DashboardUrn and ChartUrn to support the new entities.
src/datahub/sdk/chart.py	Implements the Chart entity, including methods for setting properties and managing input datasets.
src/datahub/sdk/_shared.py	Updates type aliases to include ChartUrn and DashboardUrn.
src/datahub/sdk/_all_entities.py & init.py	Registers and exports the new Dashboard and Chart classes.
examples/library/create_dashboard_complex.py	Example demonstrating complex Dashboard creation with relationships.
examples/library/create_dashboard.py	Basic Dashboard creation example.
examples/library/create_chart_complex.py	Complex Chart example showing input dataset operations.
examples/library/create_chart.py	Basic Chart creation example.

Comments suppressed due to low confidence (1)

metadata-ingestion/examples/library/create_dashboard_complex.py:30

• The Dashboard constructor is passed an extra 'dashboards' field which is not supported by the current Dashboard API. Consider removing this parameter or using a supported method to set related dashboards.

dashboards=[dashboard1.urn],

[sgomezvillamor]

Overall it looks great!
I left some minor suggestion and a question about patching

[sgomezvillamor]

input_datasets[2] >> chart

Do you think an operator like that would improve clarity? 🤔

Just an idea that came to mind. Could be backlog material if it seems useful.

[sgomezvillamor]

I just did a more detailed review and left a few comments. I might’ve been a bit picky in some cases, just trying to be helpful 😅

One thought that came to mind while reviewing: for the lineage methods, we currently have separate set|add|remove methods for each entity. eg add_input_datasets, add_charts, etc.

Have we considered a more generic approach like a unique add|set method that takes a union of supported types and internally figures out where to add them? I understand this might not work as well for set operations, but I thought it might be worth sharing in case it wasn’t explored during the design discussions.

[hsheth2]

Had a couple things to add on top of sergio's thorough review

[sgomezvillamor]

🏆