Make var naming a little more consistent in dag processor#46341
Merged
jedcunningham merged 1 commit intoapache:mainfrom Feb 1, 2025
Merged
Make var naming a little more consistent in dag processor#46341jedcunningham merged 1 commit intoapache:mainfrom
jedcunningham merged 1 commit intoapache:mainfrom
Conversation
dstandish
requested review from
ephraimbuddy and
jedcunningham
as code owners
dstandish
added
the
full tests needed
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.
dstandish
force-pushed
the
dag-processor-renames-cleanups
branch
from
ee066a4 to
09e3e97
Compare
jedcunningham
approved these changes
Feb 1, 2025
amoghrajesh
pushed a commit
to astronomer/airflow
that referenced
this pull request
Feb 3, 2025
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Feb 3, 2025
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.
niklasr22
pushed a commit
to niklasr22/airflow
that referenced
this pull request
Feb 8, 2025
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.
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.
Previously we dealt with filepaths, just string paths. Now we deal with a different object, DagFileInfo which is basically bundle name and rel path. Updating the names of some of these functions and variables makes it a little more intuitive to deal with.