refactor: 使用 ApiMessage 统一错误响应格式
- 在多个控制器中引入 ApiMessage,替换原有的 ApiResponse 错误处理逻辑,确保错误信息的一致性与可读性。 - 更新错误返回信息,使用更具语义的键值,提升 API 的可维护性与用户体验。 - 适配相关控制器的请求参数,确保在处理错误时能够正确返回相应的错误信息。
This commit is contained in:
@@ -4,6 +4,7 @@ namespace App\Http\Controllers\Api\V1\Admin\Player;
|
||||
|
||||
use App\Models\Player;
|
||||
use App\Lottery\ErrorCode;
|
||||
use App\Support\ApiMessage;
|
||||
use App\Support\ApiResponse;
|
||||
use Illuminate\Http\Request;
|
||||
use Illuminate\Http\JsonResponse;
|
||||
@@ -29,12 +30,7 @@ final class AdminPlayerDestroyController extends Controller
|
||||
->exists();
|
||||
|
||||
if ($hasWallets) {
|
||||
return ApiResponse::error(
|
||||
'该玩家钱包仍有余额,请先清空后再删除',
|
||||
ErrorCode::ValidationFailed->value,
|
||||
null,
|
||||
422,
|
||||
);
|
||||
return ApiMessage::errorResponse($request, 'admin.player_wallet_balance_blocks_delete', ErrorCode::ValidationFailed->value, null, 422);
|
||||
}
|
||||
|
||||
$hasTickets = Player::query()
|
||||
@@ -43,12 +39,7 @@ final class AdminPlayerDestroyController extends Controller
|
||||
->exists();
|
||||
|
||||
if ($hasTickets) {
|
||||
return ApiResponse::error(
|
||||
'该玩家存在注单记录,无法删除',
|
||||
ErrorCode::ValidationFailed->value,
|
||||
null,
|
||||
422,
|
||||
);
|
||||
return ApiMessage::errorResponse($request, 'admin.player_has_tickets_blocks_delete', ErrorCode::ValidationFailed->value, null, 422);
|
||||
}
|
||||
|
||||
$player->wallets()->delete();
|
||||
|
||||
Reference in New Issue
Block a user