From 31e3340cd5b4e2f168122c8f7505a876e8ca23f4 Mon Sep 17 00:00:00 2001 From: "J. Degand" <70610011+jdegand@users.noreply.github.com> Date: Thu, 18 Apr 2024 23:25:48 +0000 Subject: [PATCH 1/2] content: fix typos & add note about migrations --- content/general/use-latest-version-of-everything.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/general/use-latest-version-of-everything.md b/content/general/use-latest-version-of-everything.md index df677d9..7ccc603 100644 --- a/content/general/use-latest-version-of-everything.md +++ b/content/general/use-latest-version-of-everything.md @@ -7,11 +7,13 @@ author: # Problem -The Angular team and community are continually improving the ecosystem to make it easier to build applications. Both the performance and the compiler (e.g Ivy Renderer) are constantly being improved for better web applications. +The Angular team and community are continually improving the ecosystem to make it easier to build applications. Both the performance and the compiler (e.g., Ivy Renderer) are constantly being improved for better web applications. -Angular uses semantic versioning (semver) which means they use a regular schedule of releases. This includes a major release every six month, 1-3 minor releases for each major release, and a patch release almost every week. It's important to keep up with major releases as they contain significant new features. The longer we wait to update our application, the more expensive will be a future update. Be aware, that major releases may contain breaking changes. +Angular uses semantic versioning (semver), which means they use a regular schedule of releases. This includes a major release every six months, 1-3 minor releases for each major release, and a patch release almost every week. It’s important to keep up with major releases, as they contain significant new features. The longer we wait to update our application, the more expensive a future update can be. **Be aware** that major releases may contain breaking changes. -In addition, when API's get deprecated they remain present in the next two major releases until they are removed. Again, if we wait to long, it's likely that the update requires much more work. You can read more about deprecations in the [changelog](https://github.com/angular/angular/blob/master/CHANGELOG.md). +In addition, when APIs are deprecated, they remain present in the next two major releases until they are removed. Again, if we wait too long, it’s likely that the update will require much more work. You can read more about deprecations in the changelog. + +**Note:** In the case of significant refactors, the Angular team may create schematics that can help update your app for you. At present, there are [schematics] (https://angular.dev/reference/migrations) that convert to standalone components, the new control flow syntax, and more. # Solution From edc263cc7433274d4c4145e5553904dbda8957c6 Mon Sep 17 00:00:00 2001 From: "J. Degand" <70610011+jdegand@users.noreply.github.com> Date: Thu, 18 Apr 2024 23:29:51 +0000 Subject: [PATCH 2/2] fix: change the to an --- content/general/use-latest-version-of-everything.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/general/use-latest-version-of-everything.md b/content/general/use-latest-version-of-everything.md index 7ccc603..ceaa99d 100644 --- a/content/general/use-latest-version-of-everything.md +++ b/content/general/use-latest-version-of-everything.md @@ -11,7 +11,7 @@ The Angular team and community are continually improving the ecosystem to make i Angular uses semantic versioning (semver), which means they use a regular schedule of releases. This includes a major release every six months, 1-3 minor releases for each major release, and a patch release almost every week. It’s important to keep up with major releases, as they contain significant new features. The longer we wait to update our application, the more expensive a future update can be. **Be aware** that major releases may contain breaking changes. -In addition, when APIs are deprecated, they remain present in the next two major releases until they are removed. Again, if we wait too long, it’s likely that the update will require much more work. You can read more about deprecations in the changelog. +In addition, when APIs are deprecated, they remain present in the next two major releases until they are removed. Again, if we wait too long, it’s likely that an update will require much more work. You can read more about deprecations in the changelog. **Note:** In the case of significant refactors, the Angular team may create schematics that can help update your app for you. At present, there are [schematics] (https://angular.dev/reference/migrations) that convert to standalone components, the new control flow syntax, and more.