Automattic / Automattic/harper

"to complicated" not flagged for "too complicated" but "to complicate"

Open
#3,635 0 comments 0 reactions 0 assignees View on GitHub
bug harper-core linting
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
106

Description

Image

> way to complicated for a simple introduction example

I'm not sure if both linters detect this and the "wrong" one has the higher priority, or just gets picked randomly, or if the "right" linter doesn't kick in for this one.

This could very well be another case where consolidating the suggestions from multiple linters would be the best idea.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by reproducing the example “way to complicated for a simple introduction example” and trace which linters produce the competing suggestions. Done means the intended “too complicated” correction is selected consistently, or the issue’s proposed diagnostic consolidation is addressed with coverage for this example.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.