feat(core): add eslint vscode extension on eslint init #28573
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 2a98d28. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
|
locally build and tests are OK |
MrG9090
approved these changes
Oct 23, 2024
leosvelperez
requested changes
Nov 14, 2024
There was a problem hiding this comment.
Thanks for the contribution!
This makes sense, but let's revert these changes in the @nx/workspace:new generator and instead, add the extension in the @nx/eslint:init generator. You can check how we do this in other generators (e.g. https://github.com/nrwl/nx/blob/master/packages/jest/src/generators/configuration/lib/update-vscode-recommended-extensions.ts).
|
@leosvelperez OK thank you, I will change it |
pumano
force-pushed
the
feat/add-eslint-extension-to-new-project
branch
from
d90c933 to
32a312f
Compare
pumano
changed the title
leosvelperez
requested changes
Nov 15, 2024
pumano
force-pushed
the
feat/add-eslint-extension-to-new-project
branch
from
32a312f to
a42d533
Compare
pumano
force-pushed
the
feat/add-eslint-extension-to-new-project
branch
from
a42d533 to
2a98d28
Compare
FrozenPandaz
pushed a commit
that referenced
this pull request
Nov 15, 2024
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> when create fresh angular or react integrated project no eslint extension out of the box. Few years ago I fill the issue #7047 about deprecated tslint extension looks like that has been deleted but without change to eslint extension ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> when I create angular / react project eslint extension should be added to recommended vscode extensions ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes # (cherry picked from commit 0d6ad2b)
nartc
pushed a commit
that referenced
this pull request
Nov 15, 2024
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> when create fresh angular or react integrated project no eslint extension out of the box. Few years ago I fill the issue #7047 about deprecated tslint extension looks like that has been deleted but without change to eslint extension ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> when I create angular / react project eslint extension should be added to recommended vscode extensions ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
when create fresh angular or react integrated project no eslint extension out of the box. Few years ago I fill the issue #7047 about deprecated tslint extension looks like that has been deleted but without change to eslint extension
Expected Behavior
when I create angular / react project eslint extension should be added to recommended vscode extensions
Related Issue(s)
Fixes #