Enable Even More PyDocStyle Checks

[ferruzzi]

Description

Followup to #10742

We use Ruff to enforce docsting style

airflow/pyproject.toml

Lines 47 to 74 in 23b8e83

	extend-select = [
	"I", # Missing required import (auto-fixable)
	"UP", # Pyupgrade
	"RUF100", # Unused noqa (auto-fixable)
	# implicit single-line string concatenation
	"ISC001",
	# We ignore more pydocstyle than we enable, so be more selective at what we enable
	"D101",
	"D106",
	"D2",
	"D3",
	"D400",
	# "D401", # Not enabled by ruff, but we don't want it
	"D402",
	"D403",
	"D412",
	"D419"
	]
	extend-ignore = [
	"D203",
	"D205",
	"D212",
	"D213",
	"D214",
	"D215",
	"E731",
	]

We follow pep257 style (http://www.pydocstyle.org/en/stable/error_codes.html) for checks.

Currently, we ignore the following rules and should work towards enabling them:

Missing Docstrings

• D100 | Missing docstring in public module Add some context comments to pyproject.toml #40741
• D102 | Missing docstring in public method https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D103| Missing docstring in public function https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D104 | Missing docstring in public package Add some context comments to pyproject.toml #40741
• D107 | Missing docstring in __init__ https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D214 | Consistent multi-line docstring indentation
• D215 | Enforce number of underscores if you use underlines in a multi-line docstring
• PT004 | Fixture does not return anything, add leading underscore
• PT006 | @pytest.mark.parametrize names should be a tuple
• PT007 | @pytest.mark.parametrize values should be a tuple
• PT011 | pytest.raises() is too broad, set the match parameter
• TCH003 | stdlib imports which are only used for typechecking go in to TYPE_CHECKING block

It would be good if we can enable them one by one -- separate PRs are ok

Rough process to fix these

0. Set up your dev environment [docs]
   0.5. Go to your airflow directory and run ruff check. Write down the number of failures. Mine currently says 8. This step is just to make sure it's working and give you a baseline.

1. Open /airflow/pyproject.toml

2. In the ignore list (currently starting on line 301) comment out the rule you intend to work on

3. In a terminal, go to the airflow directory and run ruff check again. It should now fail with WAY more errors. Mine currently says 863. If the number didn't go way up, something is wrong with your setup.

4. Have a quick scroll through that list, paying attention to which ones failed because of the rule you just enabled.

5. Come up with a rough plan to break that down into bites. Maybe pick one directory that has a bunch of failures and start fixing there.

6. After you have a handful of fixes done: remove your comment (so it is ignored again) and submit a PR with that chunk of changes (see the Contributing docs in step 0)

PLEASE submit these in many small PRs. If you do it all at once it will turn into a 3000-line PR and nobody will review it. Eventually, on the last chunk you'll just remove that line from the ignore list entirely when there are no more violations to fix.

Let me know if you need any help, or ask in the Slack server.

[ferruzzi]

I included D107 in the list because it was part of the original plan in #10742, but I'd like to argue for dropping it. I don't feel that a docstring in every __init__ method is helpful at all. We're going to just copy/paste something like "Construct the {Class Name} object." a billion times.

[rohithkanchukatla]

Hi Ferruzzi, Can I take up this issue?

[potiuk]

Feel Free.

[ferruzzi]

Please do! You don't even need to take the whole thing. In fact, this is much easier to do in small chunks. Fix all the D100 changes in one area, submit the PR, fix another area, submit that pr, etc. then move on to D102 and start over, etc. Small PRs are easier for folks to review and more likely to get merged quickly.

This could (should?) easily be a team project for a bunch of people, just take bites out of it when and where you can.

Feel free to hit me up on Slack if you need a hand getting started.

[ferruzzi]

You know what, I'm just going to make the call and drop D107 off this list. If someone wants to do it, they are welcome to but I won't consider it a requirement to close this project. 👍

[ferruzzi]

After some discussion on the mailing list it looks like D102 and D103 are minimal benefit, but we do have a few others we'd like to enable and a couple that are still being discussed. I'll update the original description with details.