> > > Also regarding just adding the code snippet inline in the docs, rather > than importing from the DAG: The nice thing about having it come from the > system test DAG is that the code snippet stays up to date. Even if the task > is being skipped, at least linters, static analysis, or failures due to API > changes during parsing will get caught if it is "live code". >
Plus - all the example dags are imported during unit tests in our CI environment (it's part of the "Always" tests), so at least we know they will not generate import errors when parsed.
