-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(misc): ensure plugins are not creating workspace context while creating nodes #26253
Conversation
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 ef5c4b5. 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. |
f6b637d
to
696c588
Compare
696c588
to
68f8577
Compare
68f8577
to
0b154f6
Compare
0b154f6
to
f95862f
Compare
f95862f
to
9d88946
Compare
6a38e6b
to
0445036
Compare
0445036
to
16754df
Compare
@@ -25,6 +26,8 @@ describe('@nx/jest/plugin', () => { | |||
configFiles: [], | |||
}; | |||
|
|||
setWorkspaceRoot(tempFs.tempDir); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: is this needed? AFAICT, we already do this in the TempFs
constructor: https://github.com/nrwl/nx/blob/master/packages/nx/src/internal-testing-utils/temp-fs.ts#L30-L32.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, this came from the throw 💩 at the wall and see what sticks debugging portion of development 😅.
I've confirmed its not needed, and removed.
16754df
to
64d03a6
Compare
64d03a6
to
3859e9a
Compare
3859e9a
to
88fa1c4
Compare
}); | ||
|
||
it('should run successfully', async () => { | ||
await expect(filterGenerator(tree, options)).resolves.not.toThrowError(); | ||
await filterGenerator(tree, options); | ||
expect(true).toBe(true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove please
6f09598
to
9d8c7d0
Compare
9d8c7d0
to
ef5c4b5
Compare
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. |
…eating nodes
Current Behavior
Some plugins utilize
globWithWorkspaceContext
to perform a glob search duringcreateNodes
. This works fine without plugin isolation, and would still "work" with it, but when plugins are isolated they don't share a workspace context. Combine this with the daemon and we have issues.Expected Behavior
If the daemon is enabled, its workspace context is utilized when performing glob searches
Related Issue(s)
Fixes #