From 8d9a050ad634b7e4506b6cd8199138a02cbae968 Mon Sep 17 00:00:00 2001 From: sbwalker Date: Mon, 12 Feb 2024 08:51:41 -0500 Subject: [PATCH] Resolve issue where components are not being rendered interactively --- Oqtane.Client/UI/RenderModeBoundary.razor | 2 +- Oqtane.Shared/Models/Route.cs | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/Oqtane.Client/UI/RenderModeBoundary.razor b/Oqtane.Client/UI/RenderModeBoundary.razor index b82f9da8..a0ab867e 100644 --- a/Oqtane.Client/UI/RenderModeBoundary.razor +++ b/Oqtane.Client/UI/RenderModeBoundary.razor @@ -1,5 +1,5 @@ @namespace Oqtane.UI -@inject SiteState ComponentSiteState // can refer to either a static or interactive SiteState - it depends on the render mode +@inject SiteState ComponentSiteState @inject IStringLocalizer Localizer @inject ILogService LoggingService @inherits ErrorBoundary diff --git a/Oqtane.Shared/Models/Route.cs b/Oqtane.Shared/Models/Route.cs index 7d5b8833..56dcc3b1 100644 --- a/Oqtane.Shared/Models/Route.cs +++ b/Oqtane.Shared/Models/Route.cs @@ -9,6 +9,11 @@ namespace Oqtane.Models /// public class Route { + /// + /// parameterless constructor to prevent deserialization exceptions + /// + public Route() { } + /// /// default constructor /// the route parameter can be obtained from NavigationManager.Uri on client or HttpContext.Request.GetEncodedUrl() on server