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 "surveys/ " to "ignorePaths" array in cspell.json #5847

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

Add "surveys/ " to "ignorePaths" array in cspell.json #5847

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

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started Page.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

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 surveys/ 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
@jphamtv jphamtv added Draft Issue is still in the process of being created and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 19, 2024
@jphamtv

This comment was marked as resolved.

@freaky4wrld freaky4wrld added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Draft Issue is still in the process of being created labels Apr 21, 2024
@jphamtv jphamtv added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 22, 2024
@ShamaaTabassum ShamaaTabassum self-assigned this Apr 27, 2024
Copy link

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

@ShamaaTabassum
Copy link
Member

Availability:Today!
ETA: Today I'll complete this issue.

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
Development

Successfully merging a pull request may close this issue.

4 participants