Automattic / Automattic/harper

Need to flag present participles/gerunds of phrasal verbs written without the space.

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

Description

While Googling for examples of another kind of error on GitHub I was surprised to come across the mistake ***logining***.

Mixing up phrasal verbs and compound nouns is common in the present tense vs singular case (see #384), but until now I thought it was rare for people to do this with inflected forms.

Here are examples:
- I succeeded **logining** in after some trials
- APIs for **loginning** some websites by using requests.
- You wanna an one-key way of **logining** into , let's say, http://jwts.hit.edu.cn ?
- A simple **logining** system designing with html, css and javascript also can add the python flask and php model
- **Logining** PDNS recursor and DNSDist
- **Logining**-in should not bring you to home page
- iscsiadm tool reported error message while **logining** to 128 SPDK iSCSI target nodes
- Slowness + possible memory leak when re-**logining** to kerberos
- a python script for **loginning** Yangtze University and grabing accounts whose password isn't change.

Almost every example sentence is rife with other English mistakes, so this is probably only made by nonnative speakers. Note that when the preposition/particle ends with a single vowel followed by a single consonant as does "in", there is variance between people doubling the consonant of not, so for "log in"/"login" both "logining" and "loginning" are found

Contributor guide

Open the contributing guide

Research direction

Issue #384 is the only related entry point named; start by reading it alongside the listed log in/login examples and the note about consonant doubling. Define the accepted and flagged forms, then add coverage in the repository's existing grammar-rule tests and verify each reported form is detected without flagging valid usage.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.