-
Notifications
You must be signed in to change notification settings - Fork 12k
Bug: ng update tries to apply original template to my existing code during upgrade #4360
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
Comments
|
@intellix Good catch on the lint ... that was the one file I had to do manual surgery on, and i did move the new i update the issues above, as the others remain |
The current plan is to remove the command altogether #4416 |
Closing in favor of #4360, which 'solves' the issue. |
Hi ,Thank you for a great job thay you do .Sir can you help me please ,I download the code from "https://github.com/johnpapa" but i can't run it do you could show me the steps to execute the code |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm sharing this full console output of when I tried to update an app written in
angular-cli@beta.26
to@angular/cli@beta.29
.First, I had to manually edit the
package.json
to change the dependency name due to the name change. This is understandable as it is a one time name change, so no problem there. Once I did that, i ranng update
.My Steps
ng update
Problems
Some files (the ones that came with original template) tried to append or overwrite my files. This was bad so I skipped these. There were several (as you can see below). This is a problem that should be fixed.
The
angular-cli.json
had some valid new additions, but it also tried to remove some of mine. For this file I skipped it and then manually edited it. I think this may be OK ... wasn't hard, and I'm not sure how we can merge these without conflicts. Maybe the best course on this file is to just show the diff and ask the user to manually merge?ng lint
now yields ... "No lint config(s) found. If this is not intended, run "ng update"." -- FIXED ... error was due to copying the
lint
section tot he wrong level in theangular-cli.json
Version Info
ng update experience
The text was updated successfully, but these errors were encountered: