-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: 콜백 단건 조회 로직 개선 #123
Merged
Merged
Feat: 콜백 단건 조회 로직 개선 #123
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
callback.getAssignedMemberId().equals(memberId) 이 조건을 만족한다면 callback.getAssignedMemberId()이 null일 수 없고 "callback.getAssignedMemberId() != null" 를 무조건 만족하기 때문에 이 조건은 빼도 같은 로직으로 작동하지 않을까요?
if (callback.getAssignedMemberId().equals(memberId)) {
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
의견 감사드립니다! 사실 수정 전에는 은선님이 제안주신 코드를 사용하였었는데 NullPointException 이 발생해서 수정하게되었습니다. 예외 발생의 이유를 설명드리자면
가정: callback 은 아직 할당이 안되어
assignedMemberId = null
인 상황callback.getAssignedMemberId().equals(memberId)
이것만 있을경우,callback.getAssignedMemberId()
이null
이라서null.equals(memberId)
가 되어NullPointException
이 발생하는것으로 파악이 됩니다.그래서
callback.getAssignedMemberId() != null
로 미리 null을 확인하여 예외 발생을 방지해 보았습니다!callback.getAssignedMemberId() 는 null 이 있는 경우가 많기때문에
위 테스트 코드를 돌리면 아래와 같은 예외가 발생
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
아하 그런 이유가 있었네요~
예외 상황을 정확히 파악하고 수정하셨네요!😊