andrewgodwin commented on pull request #15142: URL: https://github.com/apache/airflow/pull/15142#issuecomment-812544316
I would argue that this fulfills a similar role as task groups - it's a primarily UI-focused feature, but it's also DAG metadata and should live in it. If it's not in the DAG, where would it go where it can appear both in the webserver view and in the output from `airflow dags show`? I'm open to changing the user interface here - this is just a rough idea me and @ashb discussed - but I really don't like moving to just a plain `str` as the thing we use with `>>` as it's going to make the code _significantly_ more complex to track where everything is supposed to go, especially when combined with XComArgs (which are the model I based this on). Not to mention all the typing for `>>` expects something inheriting from TaskMixin right now. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
