Updated tutorial DAGs to use named parameters - #71980
Merged
Merged
Conversation
Add MukundKulkarni to INTHEWILD
…amed-args updated tutorial dags to use named arguments
amoghrajesh
self-requested a review
August 22, 2026 16:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Some example DAGs teach an outdated coding style
Why
New users copy these examples to learn Airflow, but 5 of them use the old def f(**kwargs): kwargs["ti"] style instead of the modern def f(ti=None): style shown elsewhere — inconsistent and confusing for beginners.
Tests
All five converted to named parameters, **kwargs dropped where nothing else needs it, DAGs behave identically.