Automattic / Automattic/harper

False negative: Not flagging "there maybe" to be "there may be"

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

Description

Image

I thought we did have a linter handling this, if so it has a gap here. Context needs to be taken into account though to avoid false positives:
> Where should we pitch the tent? **There maybe**?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported "there maybe" example in the grammar checker and inspect the existing rule that handles this wording, if present. Check that the contextual question "Where should we pitch the tent? There maybe?" is not flagged while the intended correction to "there may be" is detected in appropriate contexts.】【。

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.