As we intend to use AirflowPipelineWriter as an illustrating example for how to integrate a new pipeline framework (i.e., LIN-696), we want to further enhance readability of its code. Specifically, we want to:
Factor out text composition logic into proper Jinja template(s)
Enhance code readability for AirflowPipelineWriter
Changes
[x] Move text composition logic from code into the Jinja template
[x] Clean up the Jinja template, removing outdated/irrelevant parts
[x] Use more clear and consistent variable names in code
[x] Update test snapshots accordingly (just reordering involved)
Summary
As we intend to use
AirflowPipelineWriteras an illustrating example for how to integrate a new pipeline framework (i.e., LIN-696), we want to further enhance readability of its code. Specifically, we want to:AirflowPipelineWriterChanges
Testing
CI will kick in.
Ticket(s)