后端服务
flask-blueprints-error-handling
更新于 2026-09-03
Flask · 错误处理规则
Error-handling rules for Flask: classification, typed codes and single-point mapping to user outcomes.
- 技术栈
- Flask
- 主题
- 错误处理
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Classify failures once: expected (validation, not-found) vs unexpected (bugs, dependencies down)
- ✓ Return typed errors carrying a stable code plus human-readable context
- ✓ Map errors to user-visible outcomes at the outermost layer only
✕ 常见反模式
- ✕ String matching on error messages to decide control flow
- ✕ Swallowing an error to keep the happy path green
- ✕ Leaking stack traces or internal identifiers to end users
◎ 交付前验证
- ◎ Type checker (mypy/pyright) passes with zero new suppressions
- ◎ Tests run in a clean virtual environment
- ◎ No secrets or environment values read at import time
同分类条目
36 篇后端服务
Node.js 工程规则
Node.js async rules: validated boundaries, non-blocking I/O and graceful shutdown
后端服务
NestJS 工程规则
NestJS rules: thin controllers, validated DTOs and evented module boundaries
后端服务
Spring Boot 工程规则
Spring Boot rules: constructor injection, transaction boundaries and validated input
后端服务
FastAPI 工程规则
FastAPI rules: Pydantic boundary models and dependency-injected services
后端服务
Django 工程规则
Django rules: queryset-level filtering and explicit select_related usage
后端服务
Flask 工程规则
Flask rules: blueprint-scoped config and application-factory wiring