-
Notifications
You must be signed in to change notification settings - Fork 0
♻️ refactor: 오타 수정, 오류 출력 수정 #64
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
Merged
Merged
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 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
Oops, something went wrong.
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.
이 catch 블록에서 모든 오류 타입을 명시적으로 처리해야 합니다. 특정 오류 타입만 발생할 것이라고 간주하여 나머지 처리를 생략하거나 'dead code'로 취급하는 것은 Rx 스트림의 안정성을 해칠 수 있습니다. Rx 스트림에서는 예상치 못한 오류로 인해 스트림이 종료되는 것을 방지하기 위해 모든 오류를 처리해야 하며, 사용자에게는 일반적인 메시지 대신 실제 발생한 오류의 내용을 반영하는 구체적인 메시지를 제공해야 합니다.
References