refactor(error handling): centralize error handling in middleware

- Remove specific error handling in individual routes
- Rely on centralized errorHandler middleware for consistent error handling
- Update comments to reflect new error handling approach
- Improve code maintainability and reduce duplication

Author: fulleni

routes/_middleware.dart

@@ -129,5 +129,5 @@ Handler middleware(Handler handler) {
 
       // Add other essential middleware like error handling
       .use(requestLogger()) // Basic request logging
-      .use(errorHandler()); // Removed as the file was deleted
+      .use(errorHandler()); // Centralized error handling
 }

routes/api/v1/data/[id].dart

@@ -194,30 +194,11 @@ Future<Response> onRequest(RequestContext context, String id) async {
     // --- Other Methods ---
     // Methods not allowed on the item endpoint
     return Response(statusCode: HttpStatus.methodNotAllowed);
-  } on NotFoundException catch (e) {
-    // Handle specific case where the item ID is not found
-    // This should be caught by the central error handler, but added as fallback
-    return Response(statusCode: HttpStatus.notFound, body: e.message);
-  } on HtHttpException catch (e) {
-    // Handle other known HTTP exceptions
-    // These should ideally be caught by the central error handler middleware
-    if (e is BadRequestException) {
-      return Response(statusCode: HttpStatus.badRequest, body: e.message);
-    }
-    print('HtHttpException occurred in /data/[id].dart: $e');
-    return Response(
-      statusCode: HttpStatus.internalServerError,
-      body: 'API Error: ${e.message}',
-    );
-  } on FormatException catch (e) {
-    // Handle potential JSON parsing/serialization errors during PUT
-    print('FormatException occurred in /data/[id].dart: $e');
-    return Response(
-      statusCode: HttpStatus.badRequest,
-      body: 'Invalid data format: ${e.message}',
-    );
   } catch (e, stackTrace) {
-    // Catch any other unexpected errors
+    // Catch any other unexpected errors (e.g., provider resolution, etc.)
+    // Specific HtHttpException (including NotFoundException), FormatException,
+    // and TypeError should be caught by the central errorHandler middleware
+    // or handled specifically within the PUT/POST logic for request body validation.
     print(
       'Unexpected error in /data/[id].dart handler: $e\n$stackTrace',
     );

routes/api/v1/data/index.dart

@@ -171,27 +171,10 @@ Future<Response> onRequest(RequestContext context) async {
     // --- Other Methods ---
     // Methods not allowed on the collection endpoint
     return Response(statusCode: HttpStatus.methodNotAllowed);
-  } on HtHttpException catch (e) {
-    // Handle known HTTP exceptions from the repository/client layer
-    // These should ideally be caught by the central error handler middleware,
-    // but handling here provides a fallback.
-    if (e is BadRequestException) {
-      return Response(statusCode: HttpStatus.badRequest, body: e.message);
-    }
-    print('HtHttpException occurred in /data/index.dart: $e'); // Log the error
-    return Response(
-      statusCode: HttpStatus.internalServerError,
-      body: 'API Error: ${e.message}',
-    );
-  } on FormatException catch (e) {
-    // Handle potential JSON parsing/serialization errors during POST
-    print('FormatException occurred in /data/index.dart: $e'); // Log the error
-    return Response(
-      statusCode: HttpStatus.badRequest,
-      body: 'Invalid data format: ${e.message}',
-    );
   } catch (e, stackTrace) {
-    // Catch any other unexpected errors
+    // Catch any other unexpected errors (e.g., provider resolution, etc.)
+    // Specific HtHttpException and FormatException should be caught by
+    // the central errorHandler middleware.
     print(
       'Unexpected error in /data/index.dart handler: $e\n$stackTrace',
     ); // Log the error and stack trace