From a8b252059421ac52f7623cea8cf4f7ebc32e2c52 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Tue, 1 Nov 2022 08:42:17 -0500
Subject: [PATCH] Add an additional cross-link (#27456)
---
aspnetcore/blazor/state-management.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/aspnetcore/blazor/state-management.md b/aspnetcore/blazor/state-management.md
index 97b9e56f87..3ac6b77b1a 100644
--- a/aspnetcore/blazor/state-management.md
+++ b/aspnetcore/blazor/state-management.md
@@ -451,6 +451,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
* To consume state across many components.
* If there's just one top-level state object to persist.
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
In-memory state container service
[!INCLUDE[](~/blazor/includes/state-container.md)]
@@ -896,6 +898,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
* To consume state across many components.
* If there's just one top-level state object to persist.
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
In-memory state container service
[!INCLUDE[](~/blazor/includes/state-container.md)]
@@ -1356,6 +1360,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
* To consume state across many components.
* If there's just one top-level state object to persist.
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
In-memory state container service
[!INCLUDE[](~/blazor/includes/state-container.md)]