Decide on linting rules to enable for project
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 59
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
While reviewing https://github.com/rstudio/pins-python/pull/298, we briefly discussed linter warnings for the use of error messages. It seems like this category of linting might have been enabled in the ruff select config in our pyproject.toml, since they are "EM".
I'm on board with whatever linting rules seem useful to folks, and didn't realize this category existed until today! Wanted to open this issue to move discussion on the rules here. I personally have never used the "EM" rules, but this is more out of ignorance 😅 .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pyproject.toml around the Ruff select configuration at line 117 and the linting discussion in pull request 298. Review the EM rules under consideration; done means the project has a documented decision and the selected Ruff configuration reflects it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100