Skip to content

Conversation

@wjddn279
Copy link
Contributor

@wjddn279 wjddn279 commented Feb 2, 2026

related: https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1769642556328069?thread_ts=1769631389.812549&cid=C06K9Q5G2UA

Improve: #59430

I improve the logic by checking various cases and identifying undetected or incorrectly detected scenarios from the initial version.

  • Fixed the issue where sdk.DAG(dag_id='dag_id') was not detected when used instead of DAG(dag_id='dag_id') .
  • Modified to skip checking functions defined with @task that are serialized by plain code.
  • Previously checked all functions defined within with DAG blocks, but now modified to only check functions whose names end with Operatoror Task.
  • Even if a warning occurs in a function definition, the warning is not exposed if the function is not actually called.

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant