Page MenuHomePhabricator

Evaluate (and implement) Textlint
Open, LowestPublic

Description

Background

We're humans, there are machines. Let them help us.

Textlint is an incredible powerful tool with a number of plugins that would perfectly accomplish our code quality tools

Plugins

Unconvincing plugins

Acceptance criteria

  • Evaluate Textlint on dependency, performance and its usefulness
    • Implement

Event Timeline

Volker_E renamed this task from Evaluate (and implement Textlint to Evaluate (and implement) Textlint.Oct 18 2022, 6:15 AM

Change 843867 had a related patch set uploaded (by VolkerE; author: VolkerE):

[design/codex@main] [WIP] build: Add textlint and plugins

https://gerrit.wikimedia.org/r/843867

What I think would, the dependency and performance question clarified, make sense is to rely on common-misspellings. We could start only there.

+1 for just adding common misspellings! That, plus a recommendation to use a spell checker plugin could help us a lot with typos (see T313540)

Change 843867 abandoned by VolkerE:

[design/codex@main] [WIP] build: Add textlint and plugins

Reason:

Textlint didn't find more friends. Let's abandon for now.

https://gerrit.wikimedia.org/r/843867

Not convincing to the peers. Putting on the backseat for now.

@Volker_E - can you please put an initial/proposed priority level on this task and move it to the Backlog column?
DST prioritization guidance

Volker_E triaged this task as Lowest priority.Jan 23 2023, 5:52 AM