-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix(core): handle package manager workspaces configuration in move generator #30268
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(core): handle package manager workspaces configuration in move generator #30268
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
View your CI Pipeline Execution �� for commit af4d617.
☁️ Nx Cloud last updated this comment at |
packages/workspace/src/utilities/typescript/ts-solution-setup.ts
Outdated
Show resolved
Hide resolved
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.
See comments
3c46e21
to
84276ff
Compare
…tches extra projects
84276ff
to
af4d617
Compare
…nerator (#30268) ## Current Behavior Moving a project included in the package manager workspaces setup to a new destination that's not matched by that configuration results in the project not included in the package manager workspaces setup. ## Expected Behavior Moving a project included in the package manager workspaces setup to a new destination that's not matched by that configuration should result in the new destination included in the workspaces setup. ## Related Issue(s) Fixes # (cherry picked from commit 432a645)
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. |
Current Behavior
Moving a project included in the package manager workspaces setup to a new destination that's not matched by that configuration results in the project not included in the package manager workspaces setup.
Expected Behavior
Moving a project included in the package manager workspaces setup to a new destination that's not matched by that configuration should result in the new destination included in the workspaces setup.
Related Issue(s)
Fixes #