feat: 리캡 서버 우선 저장 계약 적용 - #22
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
작업 내용
POST /v1/recap-captures가 신규 앱의 독립 리캡 원본과 공유 데이터를 한 요청에서 생성하도록 확장했습니다.createStandaloneRecap: true를 보내도록 계약해 이전 앱과 새 서버가 함께 동작할 때 중복 리캡이 생기지 않게 했습니다.POST /v1/me/migrate-local-data와 관련 검증 및 서비스를 제거했습니다.MomentLog.syncStatus필드를 제거하는 Prisma 마이그레이션을 추가했습니다. 이전 앱 호환을 위해 응답의syncStatus: synced상수는 한시적으로 유지합니다.검증
pnpm db:generatepnpm typecheckpnpm buildpnpm test:coverage68개 통과pnpm check:openapi-sync62개 operationpnpm check:no-spotify-metadatagit diff --check참고