Tech debt: Untyped Map<String, Object> in API error responses #324
Description
Description
Three API response DTOs use List<Map<String, Object>> for error/failure details, making the API contract opaque and unvalidatable by clients:
BulkStatusTransitionResponse.failed—List<Map<String, Object>>ImportResultResponse.errors—List<Map<String, Object>>SyncResultResponse.errors—List<Map<String, Object>>
Clients cannot know what keys to expect in these maps. API documentation generators (OpenAPI/Swagger) cannot describe the shape.
Recommendation: Create typed error records (e.g., BulkFailureDetail, ImportError, SyncError) with explicit fields.
Location: BulkStatusTransitionResponse.java, ImportResultResponse.java, SyncResultResponse.java
Traced Requirements
- GC-A012: Dual API Exposure
Impact
API usability — clients must guess at error response structure.