cixuuz commented on issue #4918: [AIRFLOW-4003] Extract example DAGs to separate pythons files URL: https://github.com/apache/airflow/pull/4918#issuecomment-473542322 > I am currently working on a similar PR > [PolideaInternal#77](https://github.com/PolideaInternal/airflow/pull/77) > My proposal differs in the assumptions: > a) I want to Extract all the code fragments, not just a certain group > b) I want to complete automatic tests for examples. > For the reasons of the tests, I have not finished this PR yet Thanks for sharing the current progress. Yes, your proposal is more complete and soundness. We maybe split the whole task into subtasks, because too many documentations need to be updated. In my PR, I extracted DAG related code for **tutorial, concepts**, scheduler, lineage. I saw you have finished changes on **scheduler and lineage**. I think I could focus on codes on **tutorial and concepts**. Thus, in this PR, I will 1) only extract codes on **tutorial and concepts**. 2) extract all code snippets, not only DAGs. Is it good? As for second step, we could create a new PR to add tests for all those examples. Besides, I have some questions: 1. Some code fragments are not a DAG file, such as [Kubernetes Operato](https://github.com/PolideaInternal/airflow/pull/77/files#diff-c63bdbf4e38e4a44b9023b6d79aba6d5), is example_dags a good place for those code? 2. Some code fragments are not complete, such as [dependency description](https://airflow.apache.org/concepts.html#bitshift-composition), is it necessary to extract such code? Thank you very much!
---------------------------------------------------------------- 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] With regards, Apache Git Services
