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

Add "Westside" to list of words in Code Spell Checker configuration file #5618

Closed
6 tasks done
roslynwythe opened this issue Sep 28, 2023 · 4 comments · Fixed by #5744
Closed
6 tasks done

Add "Westside" to list of words in Code Spell Checker configuration file #5618

roslynwythe opened this issue Sep 28, 2023 · 4 comments · Fixed by #5744
Assignees
Labels
Feature: Infrastructure For changes on site technical architecture feature: spelling good first issue Good for newcomers role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 28, 2023

Overview

We need to update the Code Spell Checker configuration file with false positive terms so that they are no longer marked as errors.

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
  • Do not change any configuration settings or make any spell corrections
  • Open the file cspell.json
  • Replace the line
  "words": [

with

  "words": [
      "Westside",
  • Save cspell.json and then test the change by opening '_includes/events-page/our-locations-content.html' and confirming that no Code Spell Checker errors/messages are displayed.
  • No docker testing is required. Create a Pull Request in the usual manner, with changes only to cspell.json.

Resources

Footnotes

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

  2. Code Spell Checker - VS Marketplace

@roslynwythe roslynwythe added good first issue Good for newcomers role: infrastructure Changes to site function role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Draft Issue is still in the process of being created size: 0.25pt Can be done in 0.5 to 1.5 hours labels Sep 28, 2023
@github-actions github-actions bot added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Sep 28, 2023
@github-actions

This comment was marked as outdated.

@roslynwythe roslynwythe added Feature: Infrastructure For changes on site technical architecture ready for product Ready for Prioritization and removed Draft Issue is still in the process of being created role: infrastructure Changes to site function Feature Missing This label means that the issue needs to be linked to a precise feature label. ready for product labels Sep 28, 2023
@anjolaaoluwa anjolaaoluwa added this to the x. Technical debt milestone Oct 1, 2023
@nikunjgupta609
Copy link

nikunjgupta609 commented Oct 6, 2023

Mam,
Please assign me to this issue. @ExperimentsInHonesty

@github-actions
Copy link

Hi @kevin31yu, 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 :)

@kevin31yu
Copy link
Member

Availability for this week: 8 hrs
My estimated ETA for completing this issue: 10/20/23

kevin31yu added a commit to kevin31yu/website that referenced this issue Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Infrastructure For changes on site technical architecture feature: spelling good first issue Good for newcomers role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
5 participants