Skip to content

Commit eeaa926

Browse files
authored
Blazor virtualization state changes (#19954)
1 parent d601a56 commit eeaa926

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

aspnetcore/blazor/components/virtualization.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to use component virtualization in ASP.NET Core Blazor ap
55
monikerRange: '>= aspnetcore-3.1'
66
ms.author: riande
77
ms.custom: mvc
8-
ms.date: 09/16/2020
8+
ms.date: 09/21/2020
99
no-loc: ["ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
1010
uid: blazor/components/virtualization
1111
---
@@ -153,3 +153,7 @@ For example, a grid or list that renders hundreds of rows containing components
153153
* `FetchData` component ([`Pages/FetchData.razor`](https://github.com/aspnet/samples/blob/master/samples/aspnetcore/blazor/Virtualization/Pages/FetchData.razor)): Uses the `Virtualize` component to display 25 rows of weather data at a time.
154154

155155
::: moniker-end
156+
157+
## State changes
158+
159+
When making changes to items rendered by the `Virtualize` component, call <xref:Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged%2A> to force re-evaluation and rerendering of the component.

0 commit comments

Comments
 (0)