[BE] refactor: todo 진행률 api 해당하는 todo가 없을 경우 에러가 아닌 null 반환 #627
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
📝 테스트 커버리지 리포트
|
jusung-c
deleted the
626-be-refactor-todo-진행률-api-해당하는-todo가-없을-경우-에러가-아닌-null-반환
branch
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.
#️⃣ 연관된 이슈
#626
Pull Request Type
Pull Request Checklist
📝 작업 내용
todo 진행률 api 해당하는 todo가 없을 경우 에러가 아닌 null 반환
💬 리뷰 요구사항
문제 생기면 바로 알려주세요!