JS Linting: Restructure content on VSCode extensions#29516
Merged
KevinMulhern merged 4 commits intoTheOdinProject:mainfrom May 25, 2025
Merged
JS Linting: Restructure content on VSCode extensions#29516KevinMulhern merged 4 commits intoTheOdinProject:mainfrom
KevinMulhern merged 4 commits intoTheOdinProject:mainfrom
Conversation
Will be moved to dedicated section
3 tasks
KevinMulhern
approved these changes
May 25, 2025
Member
KevinMulhern
left a comment
There was a problem hiding this comment.
Changes look great to me, thanks for doing this @MaoShizhong
Contributor
Author
|
Cheers @KevinMulhern Now that this has been merged, #29533 becomes relevant. Could I bump that issue for someone to have a look at when able to? |
Member
|
Absolutely @MaoShizhong, I'm happy to back anything that simplifies the curriculum lol. |
Contributor
Author
|
@KevinMulhern just double checking if that's the equivalent of an assignment or something else 😅 |
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because
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.
This PR
Issue
Closes #29499
Additional Information
Pull Request Requirements
location of change: brief description of changeformat, e.g.Intro to HTML and CSS lesson: Fix link textBecausesection summarizes the reason for this PRThis PRsection has a bullet point list describing the changes in this PRIssuesection