Automattic / Automattic/harper

"It's doublespeak" wrongly flagged to change to "its doublespeak"

Open
#3,034 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)
102

Description

> It's doublespeak, a reinterpretation and recast of original intent and meaning.

Image

Both are legitimate grammatically.
- **It's** doublespeak to the highest degree, it's perfect propaganda.
- Why India needs to end **its** doublespeak on the Syrian conflict

Until such time that patterns are found in surrounding context to disambiguate the intention, it's safest to never flag "it's doublespeak". In fact it's probably the more common of the two

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the report with the quoted examples, including both “It's doublespeak” and “its doublespeak,” and inspect the grammar-checking rule that flags the first phrase. Done means legitimate uses of “It's doublespeak” are no longer incorrectly flagged while the intended correction remains covered where context supports it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.