Update to angular 13 #14
Merged
Conversation
This file contains hidden or 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
|
I'm not an angular expert but the change LGTM. Can you amend the commit message with the approach you took from the upgrade(IIRC, from standup you mentioned the best approach wasn't the most straightforward) |
Everlag
approved these changes
Mar 1, 2022
Going from 9 => 13 was tricky, and after running into a few issues it seemed like it would maybe be easier to just re-initialize from the CLI and then manually move our code into the new scaffolding. Went with that approach and it seems to have worked nicely.
This has been deprecated and is now the default
third774
force-pushed
the
update-to-angular-13
branch
from
bac64cc to
75dc7d2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.