Linter: Make it possible to configure linter rules in the config file on per folder basis
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading the linked documentation on ignoring lines and disabling specific rules, then inspect how the linter currently handles comments and CLI arguments. Define how rules should be overridden for the unit testing directory and verify that private-function calls in the tests no longer produce errors without per-line comments.
Written by the indexing model from the issue text.
Description
Our project has a unit testing directory, where tests are calling private functions (they start with _). For tests code the linter reports errors, that the private functions are called, but for our project we want to ignore them.
There only way to configure the linter I found from the docs is with comments and cli args, which is not scalable for the team or the whole bunch of unit tests files with hundreds of calls.
- Dominant language
- Rust
- Stars
- 464
- Forks
- 39
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from GDQuest/GDScript-formatter
-
upstream
Difficulty 3/5 1-2 days Newbie friendliness 68/100
GDQuest/GDScript-formatter#363 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
GDQuest/GDScript-formatter#360 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GDQuest/GDScript-formatter#353 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 63/100
GDQuest/GDScript-formatter#348 · 3 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GDQuest/GDScript-formatter#341 ·
All issues in GDQuest/GDScript-formatter
Similar issues
-
security-scan
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
content good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
StudentSuite/awesome-skills-plugins-for-students#293 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
gfx-rs/wgpu-native#636 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
maintainer-needed p2 remote triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day