Files
bj_power/bj_power_mes/common/httpx/response.go
T

159 lines
7.4 KiB
Go
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
package httpx
import (
"encoding/json"
"errors"
"fmt"
"net/http"
"strings"
"bj_power_mes/internal/verr"
)
// Resp 统一返回结构
type Resp struct {
Code int `json:"code"`
Message string `json:"message"`
Data any `json:"data,omitempty"`
}
func writeJSON(w http.ResponseWriter, status int, body any) {
w.Header().Set("Content-Type", "application/json; charset=utf-8")
w.WriteHeader(status)
_ = json.NewEncoder(w).Encode(body)
}
// Ok 成功
func Ok(w http.ResponseWriter, data any) {
writeJSON(w, http.StatusOK, Resp{Code: 0, Message: "success", Data: data})
}
// OkCode 成功但自定义 message
func OkMessage(w http.ResponseWriter, message string, data any) {
writeJSON(w, http.StatusOK, Resp{Code: 0, Message: message, Data: data})
}
// friendlyMessage 把数据库底层技术错误(pq: / SQLSTATE / 约束冲突等)统一转成用户能看懂的业务提示。
// 覆盖所有出口(Fail / FailHTTP / FailErr / BadRequest / InternalError),
// 免得某个 handler 直接 err.Error() 就把 "duplicate key violates unique constraint..." 原样弹给用户。
// 分层:①已知唯一约束(23505)按表名给精确对象名 → ②其他已知 SQLSTATE 按类型给友好文案 →
// ③未识别的 pq:/SQLSTATE 兜底给通用提示(附原始错误便于排查)→ ④纯业务文本原样返回(不误伤)。
func friendlyMessage(raw string) string {
if raw == "" {
return raw
}
lower := strings.ToLower(raw)
// ① 唯一约束冲突(23505):按约束/表名给更具体的业务对象名
isDup := strings.Contains(lower, "23505") ||
strings.Contains(lower, "duplicate key") ||
strings.Contains(lower, "violates unique constraint") ||
strings.Contains(lower, "重复键") ||
strings.Contains(lower, "重复键违反唯一约束")
if isDup {
switch {
case strings.Contains(lower, "sys_config"):
return "该配置项已存在,请勿重复添加(同名模板/配置只能保存一次)"
case strings.Contains(lower, "station"):
return "该工位已存在,请勿重复添加(工位号不能重复)"
case strings.Contains(lower, "work_order") || strings.Contains(lower, "workorder"):
return "该产品工号已存在,请勿重复添加"
case strings.Contains(lower, "workpiece") || strings.Contains(lower, "_sn"):
return "该产品序号(SN)已存在,请勿重复添加"
case strings.Contains(lower, "material") || strings.Contains(lower, "product_type"):
return "该物料已存在,请勿重复添加(图号不能重复)"
case strings.Contains(lower, "daily_plan"):
return "该工单在这天已有排产,请勿重复添加"
case strings.Contains(lower, "user") || strings.Contains(lower, "username"):
return "该账号已存在,请勿重复添加"
default:
return "该记录已存在,请勿重复添加(同名或同编号的记录只能保存一次)"
}
}
// ② 其他已知 SQLSTATE / 约束类型,按错误性质给友好提示 + 怎么办
switch {
case strings.Contains(lower, "23503") || strings.Contains(lower, "violates foreign key constraint"):
return "保存失败:该记录已被其他单据引用,不能删除或改为无效值。请先处理引用它的单据再重试"
case strings.Contains(lower, "23502") || strings.Contains(lower, "violates not-null constraint") || strings.Contains(lower, "null value in column"):
return "保存失败:有必填内容未填。请检查带星号的必填项后重试"
case strings.Contains(lower, "22001") || strings.Contains(lower, "value too long") || strings.Contains(lower, "character varying"):
return "保存失败:某项内容超过允许长度。请缩短名称/备注后重试"
case strings.Contains(lower, "22003") || strings.Contains(lower, "numeric value out of range"):
return "保存失败:某项数字超出允许范围。请核对数量/数值后重试"
case strings.Contains(lower, "22p02") || strings.Contains(lower, "invalid input syntax") || strings.Contains(lower, "invalid input syntax for type"):
return "保存失败:某项数字或日期格式不正确。请检查录入内容后重试"
case strings.Contains(lower, "23514") || strings.Contains(lower, "violates check constraint"):
return "保存失败:某项内容不符合业务规则取值。请核对选项后重试"
case strings.Contains(lower, "40001") || strings.Contains(lower, "deadlock detected"):
return "保存失败:本次操作与其他操作冲突。请稍等片刻后重试"
case strings.Contains(lower, "42p01") || strings.Contains(lower, "relation") && strings.Contains(lower, "does not exist"):
return "保存失败:相关数据未就绪(表或结构不存在)。请通知维护人员初始化数据后再试"
case strings.Contains(lower, "42703") || strings.Contains(lower, "column") && strings.Contains(lower, "does not exist"):
return "保存失败:数据结构与程序版本不一致。请通知维护人员升级后再试"
case strings.Contains(lower, "08006") || strings.Contains(lower, "connection") && strings.Contains(lower, "refused") || strings.Contains(lower, "could not connect"):
return "保存失败:数据库连接不可用。请检查网络/数据库服务后重试"
}
// ③ 未归类的底层数据库错误(pq:/SQLSTATE/ent 约束):兜底友好提示,附原始错误供定位,避免吞掉线索
isDB := strings.Contains(lower, "pq:") ||
strings.Contains(lower, "sqlstate") ||
strings.Contains(lower, "ent: constraint failed") ||
strings.Contains(lower, "constraint failed") ||
strings.Contains(lower, "constraint violation")
if isDB {
return "保存失败:数据校验未通过或数据库处理异常,请核对录入内容后重试;若反复出现请把提示原文反馈维护人员(" + raw + ")"
}
// ④ 纯业务文本:原样返回,不误伤
return raw
}
// Fail 业务失败(HTTP 200,业务码非0)
func Fail(w http.ResponseWriter, code int, message string) {
writeJSON(w, http.StatusOK, Resp{Code: code, Message: friendlyMessage(message)})
}
// FailHTTP 直接返回 HTTP 错误
func FailHTTP(w http.ResponseWriter, status int, message string) {
writeJSON(w, status, Resp{Code: status, Message: friendlyMessage(message)})
}
// FailValidation 收集式校验失败(HTTP 200,code=3015,data.errors 结构化清单;
// 前端拦截器识别 3015 后用 ErrorListDialog 一次弹全,不用 ElMessage 单条)。
func FailValidation(w http.ResponseWriter, errs []verr.FieldError) {
writeJSON(w, http.StatusOK, Resp{
Code: 3015,
Message: fmt.Sprintf("保存失败,共 %d 项需要处理", len(errs)),
Data: map[string]any{"errors": errs},
})
}
// FailErr 统一错误出口:*verr.ValidationError → FailValidation 结构化;其他 error → 普通 Fail(3010)。
func FailErr(w http.ResponseWriter, err error) {
var ve *verr.ValidationError
if errors.As(err, &ve) {
FailValidation(w, ve.Errors)
return
}
Fail(w, 3010, err.Error())
}
// BadRequest 参数错误
func BadRequest(w http.ResponseWriter, message string) {
writeJSON(w, http.StatusBadRequest, Resp{Code: 400, Message: friendlyMessage(message)})
}
func InternalError(w http.ResponseWriter, message string) {
writeJSON(w, http.StatusInternalServerError, Resp{Code: 500, Message: friendlyMessage(message)})
}
func Unauthorized(w http.ResponseWriter, message string) {
writeJSON(w, http.StatusUnauthorized, Resp{Code: 401, Message: message})
}
// ParseJSON 解析请求体
func ParseJSON(r *http.Request, v any) error {
dec := json.NewDecoder(r.Body)
return dec.Decode(v)
}