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

Run VS Code Spell Checker on _includes/calendar.html #7144

Closed
9 tasks
Tracked by #5248 ...
ramitaarora opened this issue Jul 26, 2024 · 2 comments
Closed
9 tasks
Tracked by #5248 ...

Run VS Code Spell Checker on _includes/calendar.html #7144

ramitaarora opened this issue Jul 26, 2024 · 2 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Home page https://www.hackforla.org/ 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

Comments

@ramitaarora
Copy link
Member

Overview

We need to audit HfLA codebase files for spelling errors using the Code Spell Checker extension in VS Code in order to ensure site quality. Results will be categorized as misspellings or false positives in the HfLA spelling audit spreadsheet1 and will be resolved in later issues.

Action Items

  • You must use VS Code as your local text editor and install the Code Spell Checker VS Code extension2
  • Do not change any configuration settings or make any spell corrections
  • Open the file '_includes/calendar.html' and note any Code Spell Checker errors
  • Locate the file in column A ("File") of the "Page Audit" sheet. In the column labeled "Result Summary", select the appropriate option: No errors or At least one error.
  • If at least one error was reported, copy/paste each cSpell message into a separate row in the Results sheet
  • In each new row, select the appropriate value: misspelling or false positive from the "Result type" column. A false positive is a term that is not a misspelling but is not recognized by the spell checker because it is a technical term, abbreviation, acronym, URL or proper noun (name of a person, place or organization).
  • Move this issue to the Questions/In Review column and apply the label ready for dev lead

Merge Team

Resources/Instructions

Footnotes

  1. HfLA spelling audit spreadsheet - Results

  2. The recommended installation method is to install Code Spell Checker directly from the VS Code text editor, and those instructions can be found here. The extension can also be installed via the VS Code Marketplace website here.

@ramitaarora ramitaarora added Feature: Administrative Administrative chores etc. role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.5pt Can be done in 3 hours or less labels Jul 26, 2024
@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Aug 1, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the x. Technical debt milestone Aug 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty added P-Feature: Home page https://www.hackforla.org/ ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Aug 5, 2024
@ExperimentsInHonesty
Copy link
Member

@roslynwythe I don't think we are using the calendar include anymore. It used to connect to our meetup account and show upcoming meetups, but we don't do that anymore and are not going to bring it back. So I suggest we close this issue and open a new issue to remove the include.

@ExperimentsInHonesty
Copy link
Member

@ExperimentsInHonesty ExperimentsInHonesty closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda labels Sep 3, 2024
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 P-Feature: Home page https://www.hackforla.org/ 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
Projects
Development

No branches or pull requests

3 participants