业务规范之统一验证

刺骨的言语ヽ痛彻心扉 2023-07-24 11:59 16阅读 0赞

# 业务规范（统一验证） #

\#\#\#[业务规范之springboot整合swagger2][springboot_swagger2]  
\#\#\#[业务规范之统一验证][Link 1]  
\#\#\#[业务规范之统一返回体][Link 2]  
\#\#\#[业务规范之统一异常处理和统一响应][Link 3]

## 一、统一验证 ##

在dto中最字段验证：

@Data
    public class Employee { 
    
    // javax.validation.constraints.*
    
        @NotNull(message = "用户id不能为空")
        private Long id;
    
        @NotNull(message = "用户账号不允许为空")
        @Size(min = 6,max =12,message = "账号长度必须在6-12个字符之间")
        @Pattern(regexp = "^[\\\\u4E00-\\\\u9FA5A-Za-z0-9\\\\*]*$",message = "账号必须包含文字、字母和数字")
        private String account;
    
        @NotNull(message = "用户账号不允许为空")
        @Size(min = 6,max =18,message = "账号长度必须在6-18个字符之间")
        private String password;
    
        @NotEmpty(message = "用户邮箱不允许为空")
        @Email(message = "邮箱格式不正确")
        private String email;
    
        @Min(value = 18,message = "最新年龄为18岁")
        private Integer age;
    
        @NotBlank(message = "手机号不能为空")
        @Pattern(regexp = "^[1][3,4,5,6,7,8,9][0-9]{9}$", message = "手机号格式错误")
        private String mobile;
    
    }

在controller验证：

在前面加上 @Valid 注解：

@Api(description = "验证api")
    @RestController
    @RequestMapping("/employee")
    public class EmployeeController { 
    
    
        @ApiOperation(value="添加用户", notes="添加用户")
        @PostMapping("/addUser")
        public String addUser(@RequestBody @Valid Employee employee, BindingResult bindingResult){ 
    // 单独获取拦截的方法，生产环境使用 同意异常处理
         
            for (ObjectError allError : bindingResult.getAllErrors()) { 
                return allError.getDefaultMessage();
            }
            return "success";
        }
    
        @ApiOperation(value="添加用户2", notes="添加用户2")
        @PostMapping("/addUser2")
        public Employee addUser2(@RequestBody @Valid Employee employee) throws Exception { 
    // throw new Exception("测试失败");
            return employee;
        }
    
    }

[springboot_swagger2]: https://blog.csdn.net/suprezheng/article/details/105458030
[Link 1]: https://blog.csdn.net/suprezheng/article/details/105458073
[Link 2]: https://blog.csdn.net/suprezheng/article/details/105458133
[Link 3]: https://blog.csdn.net/suprezheng/article/details/105458191