fix: change all admin pages to prerender: true for WASM bootstrap
TaxBaik CI/CD / build-and-deploy (push) Successful in 5m13s
TaxBaik CI/CD / build-and-deploy (push) Successful in 5m13s
All Page components now use: @rendermode @(new InteractiveWebAssemblyRenderMode(prerender: true)) Attempted solution based on observation that Login.razor (prerender: true) works correctly while Dashboard.razor (prerender: false) fails WASM init. Result: blazor.boot.json still not generated, WASM bootstrap still fails. Indicates deeper SDK issue with ASP.NET Core 10 Preview Blazor WASM initialization mechanism, not fixable by render mode configuration alone. Changed files: - All 30+ admin Page components: prerender: false → true - Program.cs: MapRazorComponents added (required for WASM) Status: WASM bootstrap blocked at fundamental SDK level. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -18,7 +18,7 @@
|
||||
<div class="col-md-4">
|
||||
<h6 class="fw-bold">채널</h6>
|
||||
<p class="small">
|
||||
<a href="http://pf.kakao.com/_xoxchTX" target="_blank" class="btn btn-sm btn-warning me-2">카카오톡</a>
|
||||
<a href="https://pf.kakao.com/_xoxchTX" target="_blank" rel="noopener noreferrer" class="btn btn-sm btn-warning me-2">카카오톡</a>
|
||||
<a href="https://www.instagram.com/taxtory5668/" target="_blank" class="btn btn-sm btn-outline-secondary">Instagram</a>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user