Skip to content

JS Linting: Move VSCode extension info to own later section #29499

Open
@MaoShizhong

Description

@MaoShizhong

Checks

Describe your suggestion

In #27962 I only made small structural changes to make the JS Linting lesson match our lesson style guide, but the contents was largely unchanged.

Quite a few times (before and after), learners have been confused as to whether they should install the npm packages and/or use the VSCode extensions and why. It appears to come from the ESLint and Prettier sections mentioning both then only later does it talk about the need to install npm packages and the extensions being additional IDE integration tools for personal convenience.

The info about extensions can be taken out of the ESLint/Prettier sections so they only talk about the npm packages. At the end, there can be a new IDE extensions section which will hopefully make the lessons' point much clearer and easier to follow.

Path

Node / JS, Ruby / Rails

Lesson Url

https://www.theodinproject.com/lessons/node-path-javascript-linting

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

Metadata

Metadata

Assignees

Labels

Status: StaleThis issue/PR has been inactive for over 30 days and will be closed if inactivity continues

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions