pedro-cf commented on issue #67472: URL: https://github.com/apache/airflow/issues/67472#issuecomment-4817904671
> I'm not sure we want to go there. > > The graph and grid were on the left mutually exclusive on purpose. They are two different ways to "navigate" runs / tasks. While the right panel is a 'details' to investigate further. > > Maybe add a 'graph' details tab only when the left viewer is not showing the 'graph'? If left viewer is showing the graph the 'graph' tab should disappear? > > [@bbovenzi](https://github.com/bbovenzi) what do you think? The DAG Graph view is not just a dependency view for us, it is also a better version of the Task List tab. It already shows structure and context in a way the Task List does not, so it effectively replaces it for navigation and debugging. The Task List is already a tab inside the DAG run page, but it is not as useful as the Graph for how we actually work with DAGs. The main issue is Grid vs Graph. We do not treat them as alternatives. We use both at the same time. Grid is for execution across DAG runs. Graph is for understanding dependencies in the DAG. When something breaks, we constantly cross reference them: we scan Grid for patterns across runs, map the failing task in Graph, then go back to Grid to confirm behavior across other runs. When Graph replaces Grid, that loop breaks because we lose run context every time we switch back. If the concern is UI complexity, even an option (configuration/env) to keep Graph as a tab instead of replacing Grid would preserve that workflow without forcing a full redesign. -- 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]
