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 "_config.yml" to "ignorePaths" array in cspell.json #5850

Closed
4 of 6 tasks
Tracked by #5450
freaky4wrld opened this issue Nov 5, 2023 · 3 comments · Fixed by #6436
Closed
4 of 6 tasks
Tracked by #5450

Add "_config.yml" to "ignorePaths" array in cspell.json #5850

freaky4wrld opened this issue Nov 5, 2023 · 3 comments · Fixed by #6436
Assignees
Labels
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

@freaky4wrld
Copy link
Member

freaky4wrld commented Nov 5, 2023

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 editor1. The extension can also be installed via the VS Code Marketplace website2
  • In VSCode, navigate to 'cspell.json`
  • Add the path "_config.yml" 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

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

@freaky4wrld freaky4wrld added good first issue Good for newcomers Feature: Administrative Administrative chores etc. role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.25pt Can be done in 0.5 to 1.5 hours labels Nov 5, 2023
@ExperimentsInHonesty ExperimentsInHonesty added feature: spelling and removed Feature: Administrative Administrative chores etc. labels Nov 8, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the x. Technical debt milestone Nov 8, 2023
@roslynwythe roslynwythe added 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 and removed ready for dev lead Issues that tech leads or merge team members need to follow up on good first issue Good for newcomers size: 0.25pt Can be done in 0.5 to 1.5 hours labels Nov 17, 2023
@github-actions github-actions bot added good first issue Good for newcomers Feature: Administrative Administrative chores etc. ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.25pt Can be done in 0.5 to 1.5 hours and removed 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 feature: spelling labels Nov 30, 2023
@JessicaLucindaCheng

This comment was marked as outdated.

@roslynwythe roslynwythe removed ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda labels Jan 29, 2024
@aqandrew aqandrew self-assigned this Mar 5, 2024
Copy link

github-actions bot commented Mar 5, 2024

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

@aqandrew
Copy link
Member

aqandrew commented Mar 5, 2024

Availability for this week: 1 hour today, 3-4 hours Wednesday and Thursday
My estimated ETA for completing this issue: 15 minutes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Development

Successfully merging a pull request may close this issue.

6 participants