Standardizes HTTP exception handling and error logging for api.audace backend.
npx skills add https://github.com/lwilly3/api.audace --skill error-handling-lwilly3
Please help me install this Agent Skill. Skill: Error Handling Source: https://github.com/lwilly3/api.audace/tree/main/.github/skills/error-handling Command: npx skills add https://github.com/lwilly3/api.audace --skill error-handling-lwilly3
This Skill addresses inconsistencies in error reporting, silent failures, and the exposure of sensitive details like stack traces in API responses, ensuring a more robust and user-friendly error management system.
NotFoundException, PermissionDeniedException).403 Forbidden error with a clear message like "Permission denied: cannot delete user" instead of a generic error or a stack trace.Implement the standard error handling structure by raising HTTPException with appropriate status codes and detailed messages.
High-intent search queries and answers about installing and using this skill.
Standardizing API error responses involves enforcing consistent HTTP status codes, user-friendly messages, and systematic logging to prevent silent failures and stack trace exposure. This approach ensures robust exception management by defining a custom hierarchy for application-specific errors.
To stop exposing stack traces, implement standardized error handling that explicitly prohibits sensitive details in API responses. This system enforces returning consistent HTTP exceptions with user-friendly messages while logging the detailed traceability internally for debugging.
Systematic logging for caught exceptions works by capturing the error context whenever an exception is raised, providing crucial traceability for debugging. It operates alongside standardized HTTP exceptions to ensure all failures are recorded without exposing stack traces to the user.
You need custom exceptions like NotFoundException in CRUD operations when you want to enforce consistent error formats for specific application failures. Raising these custom exceptions ensures the API returns appropriate HTTP status codes, such as a 403 Forbidden for permission denied.
Yes, this error handling approach works for managing permission denied errors by utilizing a custom exception hierarchy. When a user lacks access, it consistently returns a 403 Forbidden error with a clear message like 'Permission denied: cannot delete user' instead of a generic failure.
infraspecdevReview backend error handling and observability gaps in Spring, FastAPI, Express, and Go services.
polaris-dxzAnalyze and correlate multi-source logs to detect anomalies and trends.
SnakeODiagnose ASP.NET Core startup issues in DI, middleware, and configuration.
ojrojasImplement comprehensive exception handling in ASP.NET Core Razor Pages applications.