You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/site/docs/migrations/1to2.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ title: Migrating from 1.x to 2.x
4
4
---
5
5
6
6
# Migrating from bUnit 1.x to 2.x
7
-
This document describes the changes made in bUnit 2.x that may affect existing tests written for bUnit 1.x. The old documentation for bUnit 1.x is available at: https://v1.bunit.dev.
7
+
This document describes the changes made in bUnit 2.x that may affect existing tests written for bUnit 1.x. The old documentation for bUnit 1.x is available at: https://v1.bunit.dev.
8
8
9
9
## One package to rule them all
10
-
`bunit.core` and `bunit.web` have be merged into a single package called `bunit`. The seperation was used to allow for extensibitlity, which isn't used anymore. Therefore `bunit.core` and `bunit.web` will stay on version 1.x, while `bunit` will be the only package going forward. To migrate, simply remove the `bunit.core` and `bunit.web` packages and add the `bunit` package. We don't expect many users to have used the `bunit.core` or `bunit.web` package directly, but may hit 3rd party packages that depend on them.
10
+
`bunit.core` and `bunit.web` have been merged into a single package called `bunit`. The separation was used to allow for extensibility, which isn't used anymore. Therefore `bunit.core` and `bunit.web` will stay on version 1.x, while `bunit` will be the only package going forward. To migrate, simply remove the `bunit.core` and `bunit.web` packages and add the `bunit` package. We don't expect many users to have used the `bunit.core` or `bunit.web` package directly, but may hit 3rd party packages that depend on them.
11
11
12
12
## `TestContext` renamed to `BunitContext`
13
13
@@ -26,8 +26,8 @@ The `Fake` prefix used for various fake implementations has been renamed to `Bun
26
26
*`FakeNavigationManager` to `BunitNavigationManager`
27
27
*`FakeJSRuntime` to `BunitJSRuntime`
28
28
*`FakeAuthenticationStateProvider` to `BunitAuthenticationStateProvider`
29
-
*`FakeAuthrozitationContext` to `BunitAuthorizationContext`
30
-
*`FakeuthorizationPolicyProvider` to `BunitAuthorizationPolicyProvider`
29
+
*`FakeAuthorizationContext` to `BunitAuthorizationContext`
30
+
*`FakeAuthorizationPolicyProvider` to `BunitAuthorizationPolicyProvider`
31
31
32
32
## Unified the `Render` methods
33
33
In v1 there were multiple `RenderXXX`methods (like `RenderComponent`, `Render` and `SetParametersAndRender`) that were used to render components and markup. In v2, these methods have been unified into a single `Render` method that can handle both components and markup) via the simple `Render` method:
@@ -89,7 +89,7 @@ The `DisposeComponents` method has been renamed to `DisposeComponentsAsync` and
89
89
+ await DisposeComponentsAsync();
90
90
```
91
91
92
-
##The `ComponentParameterFactory` and `ComponentParameter` has been removed
92
+
##The `ComponentParameterFactory` and `ComponentParameter` has been removed
93
93
The `ComponentParameterFactory` class has been removed (and therefore the usage of `ComponentParameter`).
94
94
Instead, use the `Render` method (and its overloads) to pass parameters to components.
0 commit comments