Should we make it part of the Airflow 3 documentation in our repo? Is there a reason why we want to keep it elsewhere?
We already have https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md and adding it there would allow others to also contribute to the rules and guidelines for others, so it seems reasonable to add it to Airflow repo, I think? On Tue, Nov 26, 2024 at 9:23 AM Tzu-ping Chung <t...@astronomer.io.invalid> wrote: > Hi all, > > I’ve been working on a couple of migration rules in Ruff. They are > currently in review, and I intend to get them merged when we figure out the > details with Ruff devs. > > In the mean time, I wrote a guide on how to implement a rule in Ruff. Feel > free to try implement a rule yourself! The guide is built not Ruff’s > contribution guide, and a very basic idea to Rust syntax (I put links to > them in the guide), so you may want to read those first as well. > > As mentioned previously in related threads, implementing the rules don’t > really need too much Airflow knowledge, but need some general Python syntax > (in particular AST) knowledge. It is also a good way to tip your toes into > Rust. It is an interesting language. > > The guide is available at: https://hackmd.io/@uranusjr/ByyCA_-m1l > > If you want to implement a rule, Wei has compiled a list of changes that > may potential need a lint rule. You should find it in a previous email on > this list. > > Regards, > TP
