add-api-route

To standardize TanStack Query hooks and API integration, you enforce a strict 4-file pattern generating shared DTO types, API client wrappers, and data-fetching hooks. This maintains consistent query key conventions, mutation invalidation, and centralized error handling across new domains.

The 4-file pattern standardizes API endpoints and React Query hooks by separating shared DTO types, API client wrappers, TanStack Query data-fetching hooks, and mutation invalidation logic. This enforces type-safe communication and consistent caching behavior for new backend domains.

Yes, this API integration approach requires specific TypeScript DTO types that strictly mirror Go backend structures. Enforcing shared type definitions prevents runtime errors and ensures type-safe communication across the frontend-backend architecture.

To handle mutation invalidation and centralized error handling for new API routes, you use standardized TanStack Query hooks. These hooks automatically manage cache invalidation and route errors according to strict architectural conventions for every new domain.

Yes, you can use this boilerplate to scaffold TanStack Query hooks, API client wrappers, and DTO types for any new backend domain. It ensures new features integrate seamlessly with existing caching and error-handling logic in your Next.js architecture.