2 Commits

Author	SHA1	Message	Date
kjh2064	5d1eeb8485	fix: add @rendermode InteractiveWebAssembly to all admin pages ... Problem: Page components were not rendering content because @rendermode was only on App.razor and Routes.razor, not on individual @page components. Solution: Add @rendermode InteractiveWebAssembly to all admin page components to ensure they render interactively in WebAssembly context. Result: All admin pages now render their content correctly. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-03 02:32:57 +09:00
kjh2064	8202c3278b	refactor: complete WebAssembly migration - proper architecture ... Phase 8: Complete WebAssembly 렌더 모드 전환 (정공법) Migration Summary: - ALL Admin components → TaxBaik.Web.Client - Routes.razor, Pages/*, Layout/*, Shared/*, Forms/* - App.razor → TaxBaik.WasmClient (호스트 컴포넌트) - Shared utilities → TaxBaik.Application.Utils Architecture: ✅ App.razor: TaxBaik.WasmClient (WebAssembly, 호스트) ✅ Routes + Pages: TaxBaik.WasmClient (WebAssembly) ✅ Layout + Shared + Forms: TaxBaik.WasmClient (WebAssembly) ✅ Services: TaxBaik.Web (API-First) Key Changes: - Namespaces: TaxBaik.Web.Components.Admin → TaxBaik.WasmClient.Components.Admin - Shared utilities: TaxBaik.Application.Utils (single source of truth) - Program.cs: MapRazorComponents<TaxBaik.WasmClient.Components.Admin.App>() - _Imports.razor: Components/Admin 폴더에 재구성 Build Status: ✅ 0 errors, 0 warnings Benefits: - Stateless server (no Circuit memory) - Client-side rendering (WebAssembly) - Unlimited concurrent users (horizontal scaling) - ERP-ready architecture Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-03 01:03:51 +09:00