Files

T

mjasin 2e23a032d3 feat(ui): Hub Navigation, Profile Dashboard and Auth Stability Fixes (#31 )

This PR implements the Hub Navigation system and the Profile Dashboard, while resolving critical session synchronization issues.

### Key Changes
- **Hub Navigation**: Introduced `MainHubLayout` with a premium glassmorphism sidebar, providing access to Dashboard, Library, Concepts Map, and Profile.
- **Profile Dashboard**: Implemented a high-fidelity Profile page (#27) with learning metrics, AI token usage tracking, and system rank visualization.
- **Stability Fixes**:
    - Resolved an infinite network loop on the `/profile` page by implementing request deduplication and in-memory caching in `IdentityService`.
    - Added environment-aware guards to prevent illegal JavaScript interop calls during server-side prerendering.
    - Implemented automatic session invalidation on `401 Unauthorized` responses to handle stale authentication states gracefully.
- **Reader Integration**: Added a "Return to Dashboard" option in the reader toolbar (#26).

Closes #26
Closes #27

Reviewed-on: #31
Co-authored-by: Marek Jasiński <jasins.marek@gmail.com>
Co-committed-by: Marek Jasiński <jasins.marek@gmail.com>

2026-05-10 17:36:35 +00:00

2.5 KiB

Raw Blame History

name, description, tags, version

name

description

NexusReader Architecture Standards

This skill defines the architectural guardrails for the NexusReader project to ensure consistency, scalability, and security.

Core Rules

1. Clean Architecture Layers

Domain: Pure business logic, entities, and enums. Zero dependencies on other layers.
Application: Use cases, MediatR handlers, and interfaces. Depends ONLY on Domain.
Infrastructure: Implementation details (DB context, AI services, Auth). Depends on Application and Domain.
Web/Mobile: Presentation layer. Depends on Application (and Infrastructure for DI setup).

Caution

Application MUST NOT depend on Infrastructure. This is a common failure mode. Always use abstractions (interfaces) in Application and implement them in Infrastructure.

2. Multi-Tenancy (Tenant Isolation)

Every entity related to user data MUST have a TenantId property.
Every query MUST filter by TenantId to prevent data leakage.
Default TenantId is "global" for shared resources.

3. Error Handling

Use FluentResults (Result<T>) for all Application services and handlers.
Avoid throwing exceptions for expected business failures; use Result.Fail().
Commands: State-changing operations. Should return Result or Result<T>.

+### 5. Async Operations (Zero Tolerance for async void) +- All asynchronous operations MUST return Task or ValueTask. +- Event handlers MUST use Func<Task> or async-compatible patterns. +- UI components MUST await all service calls and use InvokeAsync(StateHasChanged) for state updates within async contexts.

6. Database Schema Changes

Every change to a Domain entity or DbContext MUST be followed by the generation of a new EF Core migration.
Mandatory Commands:
- dotnet ef migrations add <MigrationName> --project src/NexusReader.Data --startup-project src/NexusReader.Web.New
- dotnet ef database update --project src/NexusReader.Data --startup-project src/NexusReader.Web.New
Ensure the migration is applied to all local development environments before proceeding with feature verification.

Audit Scripts

ArchCheck.sh: A shell script to scan for illegal cross-layer imports.

Reference Materials

Layer Dependency Matrix

2.5 KiB Raw Blame History