Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create initial spell check configuration file #5313

Closed
9 tasks done
Tracked by #4349 ...
roslynwythe opened this issue Aug 27, 2023 · 5 comments · Fixed by #5512
Closed
9 tasks done
Tracked by #4349 ...

Create initial spell check configuration file #5313

roslynwythe opened this issue Aug 27, 2023 · 5 comments · Fixed by #5512
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md feature: spelling role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less time sensitive Needs to be worked on by a particular timeframe
Milestone

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Aug 27, 2023

Overview

As developers introducing the use of the VSCode Code Spell Checker extension, we need to provide a folder-level configuration file cspell.json in the website folder, which will establish site spell check settings.

Action Items

  • You must use VS Code as your local text editor to install the VS Code extension for spell checking your codebase, The recommended installation method is to install Code Spell Checker directly from the VS Code text editor1. The extension can also be installed via the VS Code Marketplace website2
  • Create a new file cspell.json in the website (root) folder.
  • Copy/paste the following:
{
    "version": "0.2",
    "language": "en",
    // words - list of words to be always considered correct
    "words": [
        "collabathon"   
    ],
    "ignorePaths": [
        "node_modules",
        ".github"
    ]
}
  • Save the file then test the VSCode Spell Checker extension:
    • Open a few files in .github/workflows and confirm that no spell check errors appear
    • Open the file _includes/about-page/about-card-sustainability.html
      • Confirm that the term Collabathon is not marked as an error or unknown word
      • Confirm that the term Undebate is marked as an unknown word
  • Add/Commit the file cspell.json and proceed with a Pull Request in the usual manner

Resources/Instructions

Footnotes

  1. Installing Code Spell Checker from the VS Code text editor

  2. Code Spell Checker - VS Marketplace

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Aug 27, 2023
@github-actions

This comment was marked as outdated.

@roslynwythe roslynwythe added Draft Issue is still in the process of being created Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Aug 27, 2023
@roslynwythe
Copy link
Member Author

@ExperimentsInHonesty this is a basic configuration file and will be filled out with additional words, paths, and exclude patterns in subsequent issues.

@roslynwythe roslynwythe added Ready for Prioritization time sensitive Needs to be worked on by a particular timeframe and removed Draft Issue is still in the process of being created labels Aug 27, 2023
@anjolaaoluwa anjolaaoluwa added this to the 05. Know HFLA milestone Aug 27, 2023
@erinzz erinzz self-assigned this Sep 5, 2023
@github-actions
Copy link

github-actions bot commented Sep 5, 2023

Hi @erinzz, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@erinzz
Copy link
Member

erinzz commented Sep 5, 2023

Avail M-F 9-5
ETA: 9/11 EOD

@roslynwythe
Copy link
Member Author

Hi @erinzz please update the ETA on this issue. This issue is time-sensitive and I would like to help in any way that I can so please send me a Slack DM if you run into any problems. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md feature: spelling role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less time sensitive Needs to be worked on by a particular timeframe
Projects
Development

Successfully merging a pull request may close this issue.

4 participants