679b89ae4c
Security Validation (enhance-security-validation): - JWT secret validation with entropy checking and pattern detection - CSRF protection middleware with token generation/validation - Frontend CSRF token auto-injection for DELETE/PUT/PATCH requests - MIME type validation with magic bytes detection for file uploads Error Resilience (add-error-resilience): - React ErrorBoundary component with fallback UI and retry functionality - ErrorBoundaryWithI18n wrapper for internationalization support - Page-level and section-level error boundaries in App.tsx Query Performance (optimize-query-performance): - Query monitoring utility with threshold warnings - N+1 query fixes using joinedload/selectinload - Optimized project members, tasks, and subtasks endpoints Bug Fixes: - WebSocket session management (P0): Return primitives instead of ORM objects - LIKE query injection (P1): Escape special characters in search queries Tests: 543 backend tests, 56 frontend tests passing Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
970 B
970 B
ADDED Requirements
Requirement: Error Boundary Protection
The frontend application SHALL gracefully handle component render errors without crashing the entire application.
Scenario: Component error contained
- WHEN a render error occurs in a dashboard widget
- THEN only that widget SHALL display an error state
- AND other widgets SHALL continue to function normally
Scenario: User-friendly error display
- WHEN a component fails to render
- THEN users SHALL see a friendly error message
- AND users SHALL have an option to retry or report the issue
Scenario: Error logging
- WHEN a render error is caught by an Error Boundary
- THEN the error details SHALL be logged for debugging
- AND error context (component stack) SHALL be captured
Scenario: Recovery option
- WHEN a user sees an error fallback UI
- AND the user clicks "Retry"
- THEN the failed component SHALL attempt to re-render