修复 system 的 rpc 服务的 swagger 不分信息不展示的问题
This commit is contained in:
parent
0fcd30bbfd
commit
13936b39aa
|
@ -26,19 +26,19 @@ public interface OAuth2TokenApi {
|
|||
|
||||
@GetMapping(API_PREFIX + "/check")
|
||||
@ApiOperation("校验访问令牌")
|
||||
@ApiImplicitParam(name = "accessToken", value = "访问令牌", required = true, example = "tudou")
|
||||
@ApiImplicitParam(name = "accessToken", value = "访问令牌", required = true, dataTypeClass = String.class, example = "tudou")
|
||||
CommonResult<OAuth2AccessTokenCheckRespDTO> checkAccessToken(@RequestParam("accessToken") String accessToken);
|
||||
|
||||
@DeleteMapping(API_PREFIX + "/remove")
|
||||
@ApiOperation("移除访问令牌")
|
||||
@ApiImplicitParam(name = "accessToken", value = "访问令牌", required = true, example = "tudou")
|
||||
@ApiImplicitParam(name = "accessToken", value = "访问令牌", required = true, dataTypeClass = String.class, example = "tudou")
|
||||
CommonResult<OAuth2AccessTokenRespDTO> removeAccessToken(@RequestParam("accessToken") String accessToken);
|
||||
|
||||
@PutMapping(API_PREFIX + "/refresh")
|
||||
@ApiOperation("刷新访问令牌")
|
||||
@ApiImplicitParams({
|
||||
@ApiImplicitParam(name = "refreshToken", value = "刷新令牌", required = true, example = "haha"),
|
||||
@ApiImplicitParam(name = "clientId", value = "客户端编号", required = true, example = "yudaoyuanma")
|
||||
@ApiImplicitParam(name = "refreshToken", value = "刷新令牌", required = true, dataTypeClass = String.class, example = "haha"),
|
||||
@ApiImplicitParam(name = "clientId", value = "客户端编号", required = true, dataTypeClass = String.class, example = "yudaoyuanma")
|
||||
})
|
||||
CommonResult<OAuth2AccessTokenRespDTO> refreshAccessToken(@RequestParam("refreshToken") String refreshToken,
|
||||
@RequestParam("clientId") String clientId);
|
||||
|
|
|
@ -7,7 +7,7 @@ import lombok.Data;
|
|||
import java.io.Serializable;
|
||||
import java.util.List;
|
||||
|
||||
@ApiModel("RPC 服务 - OAuth2.0 访问令牌的校验 Response DTO")
|
||||
@ApiModel("RPC 服务 - OAuth2 访问令牌的校验 Response DTO")
|
||||
@Data
|
||||
public class OAuth2AccessTokenCheckRespDTO implements Serializable {
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@ import javax.validation.constraints.NotNull;
|
|||
import java.io.Serializable;
|
||||
import java.util.List;
|
||||
|
||||
@ApiModel("RPC 服务 - OAuth2.0 访问令牌创建 Request DTO")
|
||||
@ApiModel("RPC 服务 - OAuth2 访问令牌创建 Request DTO")
|
||||
@Data
|
||||
public class OAuth2AccessTokenCreateReqDTO implements Serializable {
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ import lombok.experimental.Accessors;
|
|||
import java.io.Serializable;
|
||||
import java.util.Date;
|
||||
|
||||
@ApiModel("RPC 服务 - OAuth2.0 访问令牌的信息 Response DTO")
|
||||
@ApiModel("RPC 服务 - OAuth2 访问令牌的信息 Response DTO")
|
||||
@Data
|
||||
@Accessors(chain = true)
|
||||
public class OAuth2AccessTokenRespDTO implements Serializable {
|
||||
|
|
|
@ -26,7 +26,7 @@ public class OAuth2TokenApiImpl implements OAuth2TokenApi {
|
|||
|
||||
@Override
|
||||
@ApiOperation("创建访问令牌")
|
||||
public CommonResult<OAuth2AccessTokenRespDTO> createAccessToken(@RequestBody OAuth2AccessTokenCreateReqDTO reqDTO) {
|
||||
public CommonResult<OAuth2AccessTokenRespDTO> createAccessToken(OAuth2AccessTokenCreateReqDTO reqDTO) {
|
||||
OAuth2AccessTokenDO accessTokenDO = oauth2TokenService.createAccessToken(
|
||||
reqDTO.getUserId(), reqDTO.getUserType(), reqDTO.getClientId(), reqDTO.getScopes());
|
||||
return success(OAuth2TokenConvert.INSTANCE.convert2(accessTokenDO));
|
||||
|
|
|
@ -8,7 +8,7 @@ import lombok.NoArgsConstructor;
|
|||
|
||||
import java.util.List;
|
||||
|
||||
@ApiModel("管理后台 - OAuth2.0 获得用户基本信息 Response VO")
|
||||
@ApiModel("管理后台 - OAuth2 获得用户基本信息 Response VO")
|
||||
@Data
|
||||
@NoArgsConstructor
|
||||
@AllArgsConstructor
|
||||
|
|
|
@ -10,7 +10,7 @@ import org.hibernate.validator.constraints.Length;
|
|||
import javax.validation.constraints.Email;
|
||||
import javax.validation.constraints.Size;
|
||||
|
||||
@ApiModel("管理后台 - OAuth2.0 更新用户基本信息 Request VO")
|
||||
@ApiModel("管理后台 - OAuth2 更新用户基本信息 Request VO")
|
||||
@Data
|
||||
@NoArgsConstructor
|
||||
@AllArgsConstructor
|
||||
|
|
Loading…
Reference in New Issue