Add "test/" to "ignorePaths" array in cspell.json

[freaky4wrld]

Overview

We need to populate the spell check configuration file with file paths that should be excluded from spell checking,

Action Items

• You must use VS Code as your local text editor and use the Code Spell Checker Extension for this issue, The recommended installation method is to install Code Spell Checker directly from the VS Code text editor¹. The extension can also be installed via the VS Code Marketplace website²
• In VSCode, navigate to 'cspell.json`
• Add the path "test/" to the end of the array "ignorePaths"
• Save 'cspell.json` and test the update by confirming that files in the specified path are not spell checked.

Merge Team

• Release the dependency on this item in Epic: Create issues to add ignorePaths to cSpell configuration file #5450
• When the last dependency is released, close Epic: Create issues to add ignorePaths to cSpell configuration file #5450 as completed.

Resources/Instructions

Introduction to JSON
Code Spell Checker
This issue is part of #5450

Footnotes

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

2. Code Spell Checker - VS Marketplace ↩

[github-actions]

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

[naveenmallemala5]

1. Availability: Mon-Fri
2. ETA: 12/14/2023

[github-actions]

@naveenmallemala5

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 11, 2023 at 11:06 PM PST.}