Skip to content

Commit 9ce9786

Browse files
docs(common): improvements on upgrade instructions
1 parent b35cc0d commit 9ce9786

File tree

4 files changed

+15
-6
lines changed

4 files changed

+15
-6
lines changed

_config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,11 @@ navigation:
3030
"common-features":
3131
title: "Common Features"
3232
position: 15
33+
"upgrade":
34+
title: "Upgrade"
35+
position: 17
36+
"upgrade/breaking-changes":
37+
title: "Breaking Changes"
3338
"how-to":
3439
title: "How To"
3540
position: 20

upgrade/breaking-changes/2-0-0.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
---
2-
title: Breaking Changes in 2.0.0
2+
title: 2.0.0
33
description: Handle the changes in the 2.0.0 major release of the Telerik UI for Blazor components.
44
page_title: Breaking Changes in 2.0.0
55
slug: changes-in-2-0-0
66
position: 1
77
---
88

9+
# Breaking Changes in 2.0.0
10+
911
In the `2.0.0` release, there are some changes in the Telerik Blazor components that have been brewing for a while due to the evolution of the framework. This article explains what they are and what you need to change.
1012

1113
A shortlist of the changes:

upgrade/breaking-changes/list.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
---
2-
title: List of Versions with Breaking Changes
2+
title: List of Versions
33
description: See which versions have breaking changes so you can take them into account when upgrading.
4-
page_title: List of Telerik UI for Blazor Versions with Breaking Changes
4+
page_title: List of Versions with Breaking Changes
55
slug: versions-with-breaking-changes
66
position: 0
77
---
88

9+
# List of Telerik UI for Blazor Versions with Breaking Changes
10+
911
This article lists the releases of the Telerik UI for Blazor product that introduce breaking changes. You may want to go through it when [upgrading]({%slug upgrade-tutorial%}) to see whether you are affected.
1012

1113
* [2.0.0]({%slug changes-in-2-0-0%})

upgrade/how-to-upgrade.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: How to Upgrade
3-
page_title: How to Upgrade the Telerik UI for Blazor Version
3+
page_title: How to Upgrade
44
description: How to Upgrade the version of the Telerik UI for Blazor package
55
slug: upgrade-tutorial
66
tags: upgrade,tutorial,changes,update
@@ -16,8 +16,8 @@ To upgrade the Telerik components, you need to update their NuGet package refere
1616

1717
>tip Before stating an upgrade of your project, you may find it useful to review the following information:
1818
>
19-
> Whether you are affected by a breaking change. The [List of Telerik UI for Blazor Versions with Breaking Changes]({%slug versions-with-breaking-changes%}) article shows which releases of our component suite have breaking changes. Review the information for the releases you go through so you can evaluate whether you will be affected by anything.
20-
> [UI for Blazor Release History](https://www.telerik.com/support/whats-new/blazor-ui/release-history) — reviewing the release notes for all releases you go through will let you see what has changed, what fixes, features and components have been implemented so you are better prepared to meet your project's challenges.
19+
> * Whether you are affected by a breaking change. The [List of Telerik UI for Blazor Versions with Breaking Changes]({%slug versions-with-breaking-changes%}) article shows which releases of our component suite have breaking changes. Review the information for the releases you go through so you can evaluate whether you will be affected by anything.
20+
> * [UI for Blazor Release History](https://www.telerik.com/support/whats-new/blazor-ui/release-history) — reviewing the release notes for all releases you go through will let you see what has changed, what fixes, features and components have been implemented so you are better prepared to meet your project's challenges.
2121
2222
## Upgrade Process
2323

0 commit comments

Comments
 (0)