You've already forked FrameTour-BE
fix(goods): 修复人脸切片状态处理逻辑
- 合并 WAITING_USER_SELECT 和 COMPLETED 状态的处理分支 - 统一查询人脸关联视频信息的逻辑 - 修正前端状态返回的一致性问题
This commit is contained in:
@@ -332,16 +332,8 @@ public class GoodsServiceImpl implements GoodsService {
|
||||
|
||||
// ==================== 第四步:根据切片完成状态返回结果 ====================
|
||||
|
||||
if (status == FaceCutStatus.WAITING_USER_SELECT) {
|
||||
// 切片已完成,但景区配置了 face_select_first=true
|
||||
// 需要等待用户手动选择模板后才开始渲染
|
||||
// 前端展示:「专属视频合成中」
|
||||
response.setStatus(VideoTaskStatus.PROCESSING.getCode());
|
||||
return response;
|
||||
}
|
||||
|
||||
if (status == FaceCutStatus.COMPLETED) {
|
||||
// 切片已完成,查询该人脸关联的视频信息
|
||||
if (status == FaceCutStatus.WAITING_USER_SELECT || status == FaceCutStatus.COMPLETED) {
|
||||
// 切片已完成(或等待用户选择),查询该人脸关联的视频信息
|
||||
List<MemberVideoEntity> taskList = videoMapper.listRelationByFace(faceId);
|
||||
if (taskList == null || taskList.isEmpty()) {
|
||||
response.setStatus(VideoTaskStatus.PENDING.getCode());
|
||||
|
||||
Reference in New Issue
Block a user