-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Investigate not requiring unintuitive requirements for pre-rendering PageTitle #38400
Copy link
Copy link
Closed
Closed
Copy link
Labels
Priority: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 ComponentsenhancementThis 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 onefeature-prerenderingIssues related to prerendering blazor componentsIssues related to prerendering blazor components
Milestone
Metadata
Metadata
Assignees
Labels
Priority: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 ComponentsenhancementThis 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 onefeature-prerenderingIssues related to prerendering blazor componentsIssues related to prerendering blazor components
Type
Fields
Give feedbackNo fields configured for issues without a type.
Pre-rendering for PageTitle requires rendering things in a specific order and relies on a _Layout.cshtml which is not very intuitive. See https://docs.microsoft.com/en-us/aspnet/core/blazor/components/prerendering-and-integration?view=aspnetcore-6.0&pivots=webassembly#prerendering-configuration for all of the steps involved here.
Possible things to look at:
a) Can we do away with requiring a separate
_Layout?b) If the first option is difficult, could we produce an error if the
PageTitlecomponent is being rendered before any other component?