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

Epic: Process results of sitewide spell check and preparing cspell configuration file #5244

Closed
5 tasks
roslynwythe opened this issue Aug 17, 2023 · 2 comments
Closed
5 tasks
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Draft Issue is still in the process of being created Feature: Refactor HTML feature: spelling Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Aug 17, 2023

Dependencies

Overview

Code Spell Checker in VSCode flags a large number of words, most of which are not misspellings but rather abbreviations and HfLA-specific terms that should be specified as valid words in the Code Spell Checker configuration file. We will build a configuration file that specifies which files and words should be excluded from spell checking, and we also need to fix misspelled words.

Action Items

  • Create issue Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248
    • Create a row for each file (html, md, json, yaml) file that contains text for display on the website and is appropriate to include in the Code Spell Check, in the HfLA spelling audit spreadsheet1
    • To exclude files from spell checking, use the setting cSpell:ignore in cspell.json
    • Create Epic for creating auditing issues
    • Each issue will cover one file.
    • The issue will require that for each word flagged as an error, if the word is actually misspelled, a row is populated in the "misspelled words" sheet. If it is a false positive, the word should be listed in the "whitelist words" sheet, if it is not already listed.
  • Create Epic for fixing misspellings
  • Create Epic for adding false positives to spell checker configuration file

Resources/Instructions

Footnotes

  1. HfLA spelling audit spreadsheet

@roslynwythe roslynwythe added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Feature: Refactor HTML size: 2pt Can be done in 7-12 hours Draft Issue is still in the process of being created Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level labels Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Audit site for spelling errors and false positives Epic: Process initial Code Spell Check results Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Process initial Code Spell Check results Epic: Initial Spell Check of Site, to update cspell configuration file Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Initial Spell Check of Site, to update cspell configuration file Epic: Initial Spell Check of website, to update cspell configuration file Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Initial Spell Check of website, to update cspell configuration file Epic: Process results of spell checking of website, to update cspell configuration file Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Process results of spell checking of website, to update cspell configuration file Epic: Process results of spell checking of website and preparing cspell configuration file Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Process results of spell checking of website and preparing cspell configuration file Epic: Process results of initial spell checking of website and preparing cspell configuration file Aug 17, 2023
@roslynwythe roslynwythe changed the title Epic: Process results of initial spell checking of website and preparing cspell configuration file Epic: Process results of sitewide spell check and preparing cspell configuration file Aug 17, 2023
@anjolaaoluwa anjolaaoluwa added this to the x. Technical debt milestone Aug 27, 2023
@roslynwythe
Copy link
Member Author

CLosed as not planned. The planned child issues were listed in #4349 (comment)

@roslynwythe
Copy link
Member Author

@ExperimentsInHonesty ExperimentsInHonesty closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Draft Issue is still in the process of being created Feature: Refactor HTML feature: spelling Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests

3 participants