[FEATURE] 페이지 불가용(PAGE_UNAVAILABLE) 처리 추가 - #47
Merged
Conversation
- ContentAnalysisStage에 statusCode, error, reason 필드 추가 - AnalysisResponse forSucceeded()에서 fetched=false 시 contentAnalysisError 노출 IssueNum #46
sunm2n
changed the title
minsoo0506
approved these changes
May 31, 2026
minsoo0506
left a comment
minsoo0506
left a comment
There was a problem hiding this comment.
넵 확인했습니다! 코멘트 남길만한 부분이 없어서 바로 머지하셔도 될 것 같습니다! 고생하셨습니다 👍
This was referenced Jun 1, 2026
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
2 participants
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.
요약
URL 검사 콜백 흐름에서 FastAPI가 전달하는
stages.content_analysis의statusCode,error,reason필드를 Spring이 역직렬화하지 못하던 문제를 수정하고, 페이지 불가용 사유를 클라이언트 응답에 노출합니다.ContentAnalysisStage에statusCode,error,reason필드 추가AnalysisResponse에contentAnalysisError필드 추가 —fetched=false일 때만 JSON에 노출 (@JsonInclude(NON_NULL))연관 이슈 및 Close 할 이슈 작성
close #46
Pull Request 체크리스트
TODO