3 Commits

Include renames

Author	SHA1	Message	Date
john-okeefe	a06c85e72a	fix(handlers): use correct route param name 'id' instead of 'libraryId' in processing issues ... Both ListProcessingIssues and GetProcessingIssueStats were reading the URL parameter 'libraryId', but the routes in internal/router/library.go define the param as ':id'. This caused both endpoints to always fail with an invalid library ID error since c.Param('libraryId') returns an empty string that can't be parsed as a UUID.	2026-04-21 21:31:00 -04:00
john-okeefe	67b3282831	fix(handlers): Correct database call parameters in processing issues handler ... Fix ResolveProcessingIssue and DeleteProcessingIssue methods to use proper parameter structs instead of individual arguments. Changes: - ResolveProcessingIssue: Use database.ResolveProcessingIssueParams struct with ID and MediaItemID fields instead of separate arguments - DeleteProcessingIssue: Wrap issueID in pgtype.UUID struct - Use map[string]any instead of map[string]interface{} for JSON responses These changes align with the sqlc-generated database interface and ensure type-safe parameter passing to the database layer.	2026-04-13 09:24:01 -04:00
john-okeefe	492892097d	feat(admin): Add processing issues management UI and API ... - Add ProcessingIssuesHandler with List and GetStats methods - Add AdminProcessingIssues template for issues dashboard - Display error/warning/info stats cards - Sort issues by severity and creation date - Add dismiss functionality for warnings and info items - Add navigate to media item functionality - Show issue type, description, and media details	2026-04-12 20:43:57 -04:00