Skip to content

docs: Use and enforce imperative mood #437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2025
Merged

Conversation

vdusek
Copy link
Contributor

@vdusek vdusek commented Mar 19, 2025

  • Currently, our docstrings use a mix of imperative and indicative moods basically randomly.
  • PEP 257 recommends using the imperative mood for the first line of docstrings, which is also enforced by the Ruff rule D401. So I believe the imperative form is more suitable for the docs purposes.
  • In most cases, I have simply changed the verb form, but a few cases required more rewording.
  • I updated the pyproject configuration to enforce it.

@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Mar 19, 2025
@vdusek vdusek added this to the 110th sprint - Tooling team milestone Mar 19, 2025
@vdusek vdusek requested a review from Pijukatel March 19, 2025 08:47
@vdusek vdusek self-assigned this Mar 19, 2025
@vdusek vdusek merged commit 6a99847 into master Mar 20, 2025
27 checks passed
@vdusek vdusek deleted the update-api-docs-format branch March 20, 2025 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants