xTr1m/RpgRoller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move Razor component logic into code-behind files

Browse Source
This commit is contained in:
Frank Tovar
2026-02-26 10:45:32 +01:00
parent 3bfeb39883
commit d0da35a68c
19 changed files with 1580 additions and 1503 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
TECH.md
View File

@@ -92,6 +92,7 @@ This pattern is a strong baseline for low to medium scale and should be the defa
### 2.6 Frontend architecture
- Blazor component tree rooted in `Components/App.razor` and `Components/Pages/Home.razor`.
- Razor components are split into markup-first `.razor` files with behavior/state in paired `.razor.cs` code-behind classes.
- `Home.razor` + `Home.razor.cs` are intentionally minimal and only manage loading/auth/workspace view-mode switching.
- Authenticated workspace UI plus workspace state/behavior are centralized in `Components/Pages/Workspace.razor`.
- Form UX state uses reusable `FormState<TModel>` containers in leaf controls (`HomeControls/*`) rather than parallel form/error/message property sets in `Home`.