fix(linter): fix migrating projects with the eslint plugin #23147
+39
−31
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 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit b212ad0. 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 6 targets
Sent with 💌 from NxCloud. |
FrozenPandaz
force-pushed
the
fix/eslint-migration
branch
5 times, most recently
from
e3a517f
to
ce8de21
Compare
FrozenPandaz
force-pushed
the
fix/eslint-migration
branch
from
ce8de21
to
b32d309
Compare
FrozenPandaz
force-pushed
the
fix/eslint-migration
branch
from
b32d309
to
b212ad0
Compare
JamesHenry
approved these changes
May 13, 2024
FrozenPandaz
added a commit
that referenced
this pull request
May 13, 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` --> ## Current Behavior <!-- This is the behavior we have today --> Creating a new project with ESLint is mistakenly creating a `eslint.base.config.js`. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Creating a new project with ESLint only creates a `eslint.base.config.js` file when the repo was originally standalone and the second project is made. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes # (cherry picked from commit 461b901)
|
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
Creating a new project with ESLint is mistakenly creating a
eslint.base.config.js.Expected Behavior
Creating a new project with ESLint only creates a
eslint.base.config.jsfile when the repo was originally standalone and the second project is made.Related Issue(s)
Fixes #