Dev-iL commented on issue #43176: URL: https://github.com/apache/airflow/issues/43176#issuecomment-4529041690
Several updates on this: - (User-facing) Ruff rules are coming along nicely. Astral seem to be fine with us adding rules as long as we don't overwhelm them (a good rule of thumb is one rule at a time) and follow the Airflow [community guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/24_proposing_best_practices_and_air_rules.rst) (mainly - achieving consensus on the devlist before submitting the implementation to Ruff). - Implementing new Ruff rules for Airflow is almost effortless using the [SKILL made for this purpose](https://gist.github.com/Dev-iL/3ee77257fff578b884a0f7492d082093); the limiting factor at the moment is a shortage of inspection ideas. It is worth mentioning we also have several [developer-facing AST rules available in the Airflow repo itself](https://github.com/apache/airflow/blob/main/scripts/ci/prek/check_migration_patterns.py), so if anyone is looking to add non-Ruff inspections, feel free to explore this technique. I think with the exception of (tooling for) the "Runtime analysis of DAGs if feasible" bullet, this open-ended issue seems mostly resolved to me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
