Automattic / Automattic/harper

Some missing suggestions & Other issues

Open
#3,027 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
102

Description

## `somewere` should suggest `somewhere` as a correction
- context: `If each run took just a minute (in reality, it was about 2.5 minutes), it would still take several hours (somewere between 6 and 14h). `
- linted as typo, but only suggests `some were` as fix

## `vibecoding`, `vibecoded` incorrectly (imo) flagged
I think it should just be accepted. `vibe-coding` and `vibe coding` are both more annoying to read imo. Feel free to dismiss this if you disagree.

## `reproducibility` incorrectly flagged
- context: `Hopefully, the results are equal, or at least very similar, so we don't lose too many points for reproducibility and can still get a good grade.`
- flagged as spelling, suggests `reproducible`

## `how` incorectly flagged, suggests adding `to`
- context: `He is a guest in this country and doesn't really know how anything works here`
- flags how, suggests: `Insert to after how (e.g., how to clone).`

## Platform
`harper.js`.
https://kraxen72.github.io/local-harper/ using harper 1.12.0.
source code: https://github.com/KraXen72/local-harper (self-promo :P)

Contributor guide

Open the contributing guide

Research direction

Reproduce the four spelling and grammar examples in harper.js with Harper 1.12.0, then trace how each word is diagnosed and suggested in the Harper source. Done means `somewere` gets the intended correction, `vibecoding` and `vibecoded` are accepted, and `reproducibility` and `how` are no longer incorrectly flagged.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rust
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.