Skip to content

Fix typos in v1 to v2 migration guide #1821

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.

Sign up for GitHub

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

Merged
linkdotnet merged 2 commits into from
Apr 2, 2026
+5 −5
Merged

Fix typos in v1 to v2 migration guide #1821

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a71768
Fix typos in v1 to v2 migration guide
matthetherington Apr 2, 2026
ebf6f2d
Fix more typos
matthetherington Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/site/docs/migrations/1to2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@ title: Migrating from 1.x to 2.x
---

# Migrating from bUnit 1.x to 2.x
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.
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.

## One package to rule them all
`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.
`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.

## `TestContext` renamed to `BunitContext`

Expand All @@ -26,8 +26,8 @@ The `Fake` prefix used for various fake implementations has been renamed to `Bun
* `FakeNavigationManager` to `BunitNavigationManager`
* `FakeJSRuntime` to `BunitJSRuntime`
* `FakeAuthenticationStateProvider` to `BunitAuthenticationStateProvider`
* `FakeAuthrozitationContext` to `BunitAuthorizationContext`
* `FakeuthorizationPolicyProvider` to `BunitAuthorizationPolicyProvider`
* `FakeAuthorizationContext` to `BunitAuthorizationContext`
* `FakeAuthorizationPolicyProvider` to `BunitAuthorizationPolicyProvider`

## Unified the `Render` methods
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:
Expand Down Expand Up @@ -89,7 +89,7 @@ The `DisposeComponents` method has been renamed to `DisposeComponentsAsync` and
+ await DisposeComponentsAsync();
```

## The `ComponentParameterFactory` and `ComponentParameter` has been removed
## The `ComponentParameterFactory` and `ComponentParameter` has been removed
The `ComponentParameterFactory` class has been removed (and therefore the usage of `ComponentParameter`).
Instead, use the `Render` method (and its overloads) to pass parameters to components.

Expand Down
Loading