-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[Blazor] Cascading Parameter that transfers across render boundaries #51969
Copy link
Copy link
Open
Labels
Pillar: Complete Blazor WebPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentscopilot-candidateenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing one
Milestone
Metadata
Metadata
Assignees
Labels
Pillar: Complete Blazor WebPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentscopilot-candidateenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing one
Type
Fields
Give feedbackNo fields configured for Feature.
This is a common point of confusion for customers, so we could add a new
SerializableCascadingValuecomponent or similar that is able to flow across component boundaries.With the requirement that the value needs to be JSON serializable and that you won't (probably) get updates (it's a 1-time thing, but maybe we can update via enhanced navigations).
The internal component we use for the render boundary can capture the serializable value providers in the hierarchy, serialize those, and expose them once it begins rendering interactively.