[REFACTOR]/#86 - Exception 구조 변경 #98
Merged
Conversation
This file contains 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
1 task
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.
🚀 개요
기존의
GeneralException과GlobalErrorCode로만 관리하던 예외처리 방식에서 도메인 별 예외처리로 변경하여 관리하도록 변경🔍 변경사항
httpStatus+ 'code+message` 구조로 변경code부분을 "PREFIX + code" 구조로 변경하여 API 연결 테스트 시, 더 직관적으로 오류의 원인을 찾을 수 있도록 변경AuthException을 던지도록 변경⏳ 작업 내용
BaseErrorCode를 이용하여 도메인 별 에러코드로 구조화httpStatus+ 'code+message` 구조로 변경code부분을 "PREFIX + code" 구조로 변경하여 API 연결 테스트 시, 더 직관적으로 오류의 원인을 찾을 수 있도록 변경AuthException을 던지도록 변경📝 논의사항
예외처리 리팩토링 과정에서 JWT 관련 Exception에 대한 처리 부분도 건드렸는데 추후에 문제가 없을 지 궁금합니다!