Sync ruff config drift with athena-archive-api #8
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ModernLeft/athena-file#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
athena-file's `ruff.toml` enforces additional rule families that the consumer (`athena-archive-api`) does not, and vice versa. Surveyed during cross-repo coupling work:
Decision needed
Either:
Recommendation: option 1. File a paired BE issue for adoption.
Acceptance criteria
Decision: keep the divergence intentional. athena-file is a smaller library-style codebase where the stricter D (docstring) / TC (type-checking imports) / TD (TODO format) rules pay off. athena-archive-api is a much bigger app codebase (130+ src files) where those would generate hundreds of low-value lint errors and add noise without commensurate benefit. The two codebases share core rules (line length 120, double quotes, ANN annotations, ignored E501/W291 in alembic) — the divergence is in optional opinion-rules.
Closing as resolved (decision documented). Future re-evaluation should weigh cost vs. benefit per rule family rather than wholesale adoption.