-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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): fix moving a project into a subfolder #14988
fix(misc): fix moving a project into a subfolder #14988
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2c5fadf
to
b7e838e
Compare
b7e838e
to
46ca2ab
Compare
46ca2ab
to
2052060
Compare
2052060
to
914be31
Compare
914be31
to
06c141e
Compare
(cherry picked from commit 3bb87ea)
Since this PR is merged, I assume this fix should have made it at least into the latest beta. I got @nrwl/workspace@15.8.0-beta.7 and tried moving a project into a subfolder. Got an error:
To reproduce:
|
hey @DmitryEfimenko! A couple of things based on your reproduction steps:
Please note the above points are solely based on the steps description. I can't access the repo you linked (is it private?). So, I was not able to reproduce the issue. If the above points are irrelevant or don't solve the issue, could you open an issue with those details and an accessible repro? The error is different than what this PR addressed. It could still be an issue caused by this PR or a follow up change, but better to create a proper issue and track it separately. |
@leosvelperez My bad, I specified the wrong repo link. Fixed it. I also tried your suggestions and still got an error. It looks like it's only for angular projects. Created a issue here |
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
The
move
generator doesn't work correctly when moving a project to a new destination that's a subfolder of its current root path. This happens because the project configuration is created in the new destination before moving the rest of the files. Because of that, when moving the files, it collects the new project configuration as a child and moves it to another nested level, which is wrong.Expected Behavior
The
move
generator should work correctly when moving a project to a new destination that's a subfolder of its current root path.Related Issue(s)
Fixes #13910