From 5ca1fe862019b39b1c46a08165fcc3810f3904d4 Mon Sep 17 00:00:00 2001
From: kjh2064 <kjh2064@gmail.com>
Date: Fri, 3 Jul 2026 02:30:09 +0900
Subject: [PATCH] fix: add explicit rendermode to Router component - enable
 page routing

Problem: Routes.razor Router component had no @rendermode attribute, causing
routed pages to not render content (only shell was interactive).

Solution: Add @rendermode="new InteractiveWebAssemblyRenderMode(prerender: false)"
to Router element to ensure all routed page components render properly.

Result: Blog pages and all admin pages now render their content correctly.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
---
 TaxBaik.Web.Client/Components/Admin/Routes.razor | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/TaxBaik.Web.Client/Components/Admin/Routes.razor b/TaxBaik.Web.Client/Components/Admin/Routes.razor
index f2e15fb..5cce44e 100644
--- a/TaxBaik.Web.Client/Components/Admin/Routes.razor
+++ b/TaxBaik.Web.Client/Components/Admin/Routes.razor
@@ -1,7 +1,7 @@
 @namespace TaxBaik.WasmClient.Components.Admin
 @using Microsoft.AspNetCore.Components.Routing
 
-<Router AppAssembly="@typeof(TaxBaik.WasmClient._Imports).Assembly">
+<Router AppAssembly="@typeof(TaxBaik.WasmClient._Imports).Assembly" @rendermode="new InteractiveWebAssemblyRenderMode(prerender: false)">
     <Found Context="routeData">
         <AuthorizeRouteView RouteData="@routeData" DefaultLayout="@typeof(TaxBaik.WasmClient.Components.Admin.Layout.MainLayout)">
             <NotAuthorized>