Skip to content

History / Frontend Structure Guidelines

Revisions

  • docs: update Frontend Structure and Guidelines; add Frontend Verification and Tooling guide; create Frontend Type Boundary pattern

    @paulushcgcj paulushcgcj committed Oct 20, 2026
  • feat: Migrate from react-router-dom to TanStack Router v1 - Replaced `react-router-dom` with `@tanstack/react-router` v1, transitioning to a static route tree with composable HOC guards. - Deleted legacy routing components: `AppRoutes.tsx`, `ProtectedRoute.tsx`, `DashboardRedirect.tsx`. - Introduced new routing structure with `routeTree.tsx` for router singleton and guard application, and `AppRouter.tsx` as a thin wrapper for `RouterProvider`. - Updated `routePaths.tsx` to use `component: ComponentType` and added `guards?: RouteGuard[]` to `RouteDescription`. - Simplified `redirectStorage.ts` to a single session storage key for post-login redirects. - Updated architecture documentation to reflect changes in routing, error handling, and component structure. - Ensured all unit tests across 14 modules were migrated to the new routing structure and passed without TypeScript errors.

    @paulushcgcj paulushcgcj committed May 11, 2026
  • docs: add Feature Flags documentation and update architecture references

    @paulushcgcj paulushcgcj committed Apr 20, 2026
  • docs: update architecture documentation with global API middleware and notification improvements

    @paulushcgcj paulushcgcj committed Apr 16, 2026
  • docs: enhance notification events documentation and update architecture overview

    @paulushcgcj paulushcgcj committed Apr 15, 2026
  • docs: centralize query hooks and improve token handling in architecture documentation

    @paulushcgcj paulushcgcj committed Apr 14, 2026
  • docs: Enhance runtime configuration and feature flags documentation with validation rules and usage examples

    @paulushcgcj paulushcgcj committed Apr 10, 2026
  • feat: Add detailed error documentation for NR Waste Plus application - Introduced new error codes and descriptions for common issues: - G405: Method Not Allowed - G408: Request Timeout - G409: Conflict - G410: Gone - G413: Payload Too Large - G415: Unsupported Media Type - G422: Unprocessable Entity - G429: Too Many Requests - G500: Internal Server Error - G501: Not Implemented - G502: Bad Gateway - G503: Service Unavailable - G504: Gateway Timeout - P403: Insufficient Permissions - R600: Data Cannot Be Retrieved - U404: User Not Registered - Created an overarching error handling guide to assist users in understanding and resolving application errors.

    @paulushcgcj paulushcgcj committed Apr 10, 2026