Decision Record: VS Code Spell Checker Extension

[jdingeman]

Overview

We need to create a Decision Record so that we have the history of why & how we are using this spelling linter so that people in the future can understand it.

Action Items

• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki

Action Items to be completed when new wiki is ready

• Create a new Decision Record in Solutions Adopted
• Follow the template to document this choice
• Be sure to include the following in your decision record:
  • Why we are using the linter
  • Why specifically this linter and what the requirements were
    • See comments in Find Linter and Matching VS Code Plugin to Spell Check Site #3546
  • Link to the extension for developers to install
  • Link to issue Create a Roll Out Plan for adding Code Spell Checker VS Code Extension #4349
  • Steps being taken to implement the linter across the team
  • Guidance on what has worked and what hasn't
    • This guidance should consider plans for implementing other local linters at a later time
• Add a link to the DR in Solutions Adopted
• Update the main Decision Records page with a link to the new DR preceded by a ✅
• Present your record to Product and Dev Leads Team for approval

For Merge Team/Dev Leads/PM

• When the DR has been accepted, release dependency on Create a Roll Out Plan for adding Code Spell Checker VS Code Extension #4349. If all dependencies have been satisfied, move that issue into the New Issue Approval column with the ready for dev lead or ready for product label for review and a note about where to find the finished plan.

Resources

• Decision Records on Solutions Adopted
• Code Spell Checker as a local linter

Decision Record Template

This is a record in the [Decision Records on Solutions Adopted](https://github.com/hackforla/website/wiki/Decision-Records-on-Solutions-Adopted).

#### Issue 
#### Problem Statement
#### Potential Solution
#### Feasibility Determination

[github-actions]

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

[amath95]

Availability: 05/07
ETA: 05/12

[github-actions]

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