-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Description
Coming from here
Problem
We have typos/misspells across the codebase. For example, I saw following typos in a single file: TASK_TITLE_WITH_OPTONAL_SHORT_MENTION, reportRecipientAcountIDs, incoke
Background
We accept many contributions from all over the world, and sometimes, it can be difficult to spot such typos during code review. This is especially true when PRs need to be merged urgently to fix important bugs or if PRs are big enough (we can't simply go through each letter in changes to assure that the codebase doesn't have typos).
Solution
We can enable tools for spell checking. The most know one is cspell . We can integrate it as a part of our eslint pipeline (https://www.npmjs.com/package/@cspell/eslint-plugin) or we can integrate it via GitHub actions as a standalone check using https://github.com/streetsidesoftware/cspell-action.
Lets investigate how long would such action run if we run it on each commit on PRs only on the files that changed.
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021876644443513097620
- Upwork Job ID: 1876644443513097620
- Last Price Increase: 2025-06-12
- Automatic offers:
- dominictb | Contributor | 106642648
Issue Owner
Current Issue Owner: @alexpensifyMetadata
Metadata
Labels
Type
Projects
Status