bbovenzi opened a new pull request, #38476:
URL: https://github.com/apache/airflow/pull/38476

   We had a bunch of complicated logic trying to separate out unconnected 
dataset "graphs" from each other in the UI. It was buggy and could cause the UI 
to crash if there were too many datasets. So I decided to refactor a few things 
wih the tools I have available:
   
   - Always render the full datasets dependencies graph
   - Merge the Dataset and DAG search bars into one, with a single selection vs 
multiselect
   - Can click to select a DAG
   - Hover on a DAG shows popover to link to it's page
   - Add loading indicator to the graph
   - Zoom the graph to the node upon selection
   - Highlight edges connected to a DAG
   
   <img width="544" alt="Screenshot 2024-03-25 at 6 56 02 PM" 
src="https://github.com/apache/airflow/assets/4600967/3e2ea7f6-3fd8-4fb5-932e-23b459b8a669";>
   
   ![Mar-25-2024 
19-03-17](https://github.com/apache/airflow/assets/4600967/5b172900-32a7-448f-ad43-f46baadeba40)
   
   
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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]

Reply via email to