Restructure project #81

Open
opened 2026-06-29 15:42:53 +01:00 by Vylpes · 1 comment
Owner
No description provided.
Vylpes added this to the 0.1.0 milestone 2026-06-29 15:42:53 +01:00
Vylpes self-assigned this 2026-06-29 15:42:53 +01:00
Vylpes added this to the 0.1 Sprint 1 project 2026-06-29 15:42:53 +01:00
Vylpes stopped working 2026-06-29 16:08:31 +01:00
21 minutes 43 seconds
Member

Spike findings — Project restructure (#81)

Exploration is complete via PR #82 (feature/restructure → release/0.1.0). Full review: #82

What the spike delivered

  1. Blazor Identity refactor — @code blocks split into .razor.cs partials; AccountLayout added for static rendering; IdentityUserAccessor introduced and registered in DI.
  2. App cleanup — template pages (Counter, Weather) removed; passkey UI removed; nav/layout simplified; authenticated users redirect to /dashboard.
  3. Product/docs foundation — ADR, PRD, epics, stories, testing guide, email providers doc added under docs/.
  4. Tooling — Forgejo issue/PR templates and Cursor skills copied in.

Verdict

The structural direction is sound and worth merging once remaining blockers in #82 are addressed. The Identity code-behind pattern and AccountLayout + NavigationManager.Refresh approach are the right shape for a maintainable Blazor Server app.

Blockers still open in #82 (must fix before merge)

# Issue Status
1 Debug instrumentation in source ✅ Fixed in 52693ca
2 Committed .cursor/debug-99de3c.log ✅ Removed; .cursor/debug*.log added to .gitignore
3 App.razor still loads deleted PasskeySubmit.razor.js (404 on every page) ❌ Open
4 IdentityUserAccessor returns after redirect without stopping execution ❌ Open
5 Remember-me logic in Login.razor.cs but checkbox removed from UI ❌ Open

Recommended follow-on work (post-merge)

Created as unassigned stories with needs/criteria for the planning runner:

  • Document intentional passkey removal for v1
  • Standardize Droplet.Auth.Components.Account vs Droplet.Components.Account.* namespaces
  • Incremental cleanup of nullable-reference and Blazor analyzer warnings

Next step

@Vylpes — please address the three remaining blockers in #82 and re-request review. Spike can be closed once #82 merges.

## Spike findings — Project restructure (#81) Exploration is complete via PR #82 (`feature/restructure` → `release/0.1.0`). Full review: https://git.vylpes.xyz/RabbitLabs/droplet-next/pulls/82 ### What the spike delivered 1. **Blazor Identity refactor** — `@code` blocks split into `.razor.cs` partials; `AccountLayout` added for static rendering; `IdentityUserAccessor` introduced and registered in DI. 2. **App cleanup** — template pages (`Counter`, `Weather`) removed; passkey UI removed; nav/layout simplified; authenticated users redirect to `/dashboard`. 3. **Product/docs foundation** — ADR, PRD, epics, stories, testing guide, email providers doc added under `docs/`. 4. **Tooling** — Forgejo issue/PR templates and Cursor skills copied in. ### Verdict The structural direction is sound and worth merging once remaining blockers in #82 are addressed. The Identity code-behind pattern and `AccountLayout` + `NavigationManager.Refresh` approach are the right shape for a maintainable Blazor Server app. ### Blockers still open in #82 (must fix before merge) | # | Issue | Status | |---|-------|--------| | 1 | Debug instrumentation in source | ✅ Fixed in `52693ca` | | 2 | Committed `.cursor/debug-99de3c.log` | ✅ Removed; `.cursor/debug*.log` added to `.gitignore` | | 3 | `App.razor` still loads deleted `PasskeySubmit.razor.js` (404 on every page) | ❌ Open | | 4 | `IdentityUserAccessor` returns after redirect without stopping execution | ❌ Open | | 5 | Remember-me logic in `Login.razor.cs` but checkbox removed from UI | ❌ Open | ### Recommended follow-on work (post-merge) Created as unassigned stories with `needs/criteria` for the planning runner: - Document intentional passkey removal for v1 - Standardize `Droplet.Auth.Components.Account` vs `Droplet.Components.Account.*` namespaces - Incremental cleanup of nullable-reference and Blazor analyzer warnings ### Next step @Vylpes — please address the three remaining blockers in #82 and re-request review. Spike can be closed once #82 merges.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Total time spent: 21 minutes 43 seconds
Vylpes
21 minutes 43 seconds
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
RabbitLabs/droplet-next#81
No description provided.